Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

Uniform distributed topics - specify subdeployments

After creating a uniform distributed topic, you can change the its 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). Uniform distributed topics and queues depend on the JMS servers they are targeted to for the management of persistent messages, durable subscribers, and message paging.

For example, you can use subdeployments to link specific server and JMS resources with the uniform distributed topic members. For example, if a JMS system module named jmssysmod-jms.xml, is targeted to three WebLogic Server instances: wlserver1, wlserver2, and wlserver3, each with a configured JMS server, and you want to target a uniform distributed topic and a uniform distributed topic to each server instance, you can group the UDQ and uniform distributed topic in a subdeployment named servergroup, to ensure that these resources are always linked to the same server instances.

To associate a uniform distributed topic with a subdeployment:

  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, navigate to the uniform distributed topic resource that you want to configure:
  3. Click the Subdeployment tab.
  4. In the Subdeployments drop-down, select a subdeployment to associate with the uniform distributed topic.

    To manage existing subdeployments in a module, use the module's Subdeployment management page. For more information, see Configure subdeployments in JMS system modules.

  5. Save your changes:
  6. 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).


Skip navigation bar   Back to Top