Use this page to create and manage subdeployments for your JMS resources. A subdeployment is a mechanism by which JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, SAF agents, or a cluster).
For example, you can group a connection factory with stand-alone 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 stand-alone queues or topics are members of a subdeployment, a connection factory can only be targeted to the same JMS server.
To manage JMS module's subdeployments:
Note: The Cluster section is available only when the JMS system module is part of a clustered WebLogic Server environment.
The new subdeployment is added to the Subdeployments table.
After you finish
If you need to change the targeting of an existing subdeployment, in the Subdeployments table click the subdeployment name, and on target settings page, select a different target and click Save.