Administration Console Online Help

1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
2. In the Administration Console, expand Services > Messaging and select JMS Modules.
3. In the JMS Modules table, click the name of JMS module in which you want to configure the connection factory resource.
4. On the module's Settings page, click the New button in the Summary of Resources table.
5. On the Create a New JMS System Module Resource page, select Connection Factory from the list of JMS resources, and then click Next.
6. On the Connection Factory Properties page, define the connection factory's basic properties:
   1. In Name, enter a name for the connection factory.

      Once you create a connection factory, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

   2. In JNDI Name, enter a name for accessing the connection factory within the JNDI name space. Applications use the JNDI Name to look up the connection factory.

      If you do not specify a JNDI name for the connection factory, it will not be available for JNDI lookup even after the connection factory has been targeted to a server resource. Therefore, you will only be able to access the connection factory in an application-scoped context.

7. Click Next to proceed to the targeting page or click Finish to create the connection factory.

   Caution: If you click Finish at this point, the connection factory will be created without any targeting information. As a result, the connection factory will not be deployed and thus will not be available to applications until you manually select a subdeployment target, as described in Specify subdeployments for connection factories.

   On the targeting page, you can either target the connection factory to system-selected JMS server(s), server instance(s), or cluster, or optionally proceed to an advanced targeting page where you can either select an existing subdeployment or create a new subdeployment. A subdeployment is a mechanism by which JMS module resources (such as standalone destinations, uniform distributed destinations, and connection factories) are grouped and targeted to server resources (such as JMS servers, server instance(s), or cluster).

8. For basic system-selected targeting, in the Targets box simply select a JMS server(s), server instance(s), or cluster, and then click Finish. A system-owned subdeployment is automatically generated for the connection factory and the selected target(s), using the BEA_JMS_SUBDEPLOYMENT_XXXX name space, where XXXX is the name of the parent module.

   Note: JMS administrators cannot create any subdeployment beginning with BEA_JMS_SUBDEPLOYMENT. This naming restriction is validated during the subdeployment creation process.

   Upon clicking Finish, the configured connection factory is added to the module's Summary of Resources table, which displays its system-generated subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.

9. For advanced targeting, click Advanced Targeting, which allows you to select an existing subdeployment or to create a new one.
   • To select an existing subdeployment for the connection factory, select one from the Subdeployments drop-down. When a valid subdeployment is selected, its targeted JMS server(s), server(s), or cluster appear as selected in the Targets box. (A subdeployment with standalone destinations can only be targeted to a single JMS server.) Click Finish to add the connection factory to the selected subdeployment.
   • To create a new subdeployment for the connection factory, click the Create a new Subdeployment button. On the Subdeployment Properties page, enter a name for the subdeployment, and then click OK. On the ensuing subdeployment targeting page, select a JMS server(s), server instance(s), or cluster in the Targets box. (A subdeployment with standalone destinations can only be targeted to a single JMS server.) Click Finish to add the connection factory to the new subdeployment.

   Upon clicking Finish, the configured connection factory is added to the module's Summary of Resources table, which displays the user-defined subdeployment name and its targets. You can also reconfigure subdeployment targets later if you wish. For more information about managing subdeployments, refer to Configure subdeployments in JMS system modules.

10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).