Specify subdeployments for connection factories

After creating a connection factory, you can change the connection factory's subdeployment, which is either a system-generated subdeployment (using the protected BEA_JMS_SUBDEPLOYMENT_XXXX name space) or a user-defined 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 a server resource (such as JMS servers, server instances, or cluster).

For example, you can group a connection factory with standalone queues or topics in a subdeployment targeted to a specific JMS server, which guarantees that all these resources are co-located to avoid extra network traffic. Another advantage of such a configuration would be if the targeted JMS server needs to be migrated to another WebLogic server instance, then the connection factory and all its connections will also migrate along with the JMS server's destinations. However, when standalone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.

To associate a connection factory with a subdeployment:

If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
In the Administration Console, navigate to the connection factory resource that you want to configure:
- Navigate to JMS Resources in System Modules
- Navigate to JMS resources in an application module
Click the Subdeployment tab.
In the Subdeployments drop-down, select a subdeployment to associate with the connection factory.
To manage existing subdeployments in a module, use the module's Subdeployment management page. For more information, see Configure subdeployments in JMS system modules.
Save your changes:
- Save Changes to JMS Resources in System Modules
- Save changes to JMS resources in an application module
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).