Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# Configure subdeployments in JMS system modules

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 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 manage JMS module's subdeployments:

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 resulting JMS Modules table, click the JMS system module in which you want to configure the subdeployment.
4. Click the Subdeployments tab.
5. Click the New button in the Subdeployments table.
6. On the Subdeployment Properties page, enter a name for the subdeployment.
7. Click Next.
8. On the Targets page:
   1. In the JMS Servers section, select each JMS server instance on which you want to deploy the resources associated with the subdeployment.
   2. In the Server section, select each server instance on which you want to deploy the resources associated with the subdeployment.
   3. In the Cluster section, select each cluster on which you want to deploy the resources associated with the subdeployment, or select specific servers within a cluster.

   Note: The Cluster section is available only when the JMS system module is part of a clustered WebLogic Server environment.

9. Click Finish.

   The new subdeployment is added to the Subdeployments table.

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).

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.