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
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
To associate a uniform distributed topic with a 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.