Specify subdeployments for topics

After creating a topic, you can change the topic'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 for JMS destinations is a mechanism by which topics and topics, and possibly connection factories, are grouped and targeted to a single JMS server. Queues and topics depend on the JMS servers they are targeted to for the management of persistent messages, durable subscribers, and message paging.

For example, if you want to co-locate a group of topics with a connection factory that is targeted to a specific JMS server, you can associate the topics with the subdeployment the connection factory belongs to, provided the connection factory is not already targeted to multiple JMS servers (for example, targeted to a server instance hosting multiple JMS servers).

To associate a topic 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 topic 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 topic.
Click Save to associate the topic with the selected subdeployment.
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).