Targeting Uniform Distributed Queues and Topics

4-12 Configuring and Managing JMS for Oracle WebLogic Server ■ UniformDistributedTopicBean The following sections provide additional uniform distributed destination information: ■ Section 4.5.2.1, Targeting Uniform Distributed Queues and Topics ■ Section 4.5.2.2, Pausing and Resuming Message Operations on UDD Members ■ Section 4.5.2.3, Monitoring UDD Members ■ Section 4.5.2.4, Configuring Partitioned Distributed Topics

4.5.2.1 Targeting Uniform Distributed Queues and Topics

Unlike standalone queue and topics resources in a module, which can only be targeted to a specific JMS server in a domain, UDDs can be targeted to one or more JMS servers, one or more WebLogic Server instances, or to a cluster, since the purpose of UDDs is to distribute its members on every JMS server in a domain. For example, targeting a UDD to a cluster ensures that a member is uniformly configured on every JMS server in the cluster. You can also use subdeployment groups when configuring UDDs to link specific resources with the distributed members. For example, if a 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 queue and a connection factory to each server instance, you can group the UDQ and connection factory in a subdeployment named servergroup, to ensure that these resources are always linked to the same server instances. Heres how the servergroup subdeployment resources would look in jmssysmod-jms.xml: weblogic-jms xmlns=http:xmlns.oracle.comweblogicweblogic-jms connection-factory name=connfactory sub-deployment-nameservergroupsub-deployment-name jndi-namejms.connectionfactory.CFjndi-name connection-factory uniform-distributed-queue name=UniformDistributedQueue sub-deployment-nameservergroupsub-deployment-name jndi-namejms.queue.UDQjndi-name forward-delay10forward-delay uniform-distributed-queue weblogic-jms And heres how the servergroup subdeployment targeting would look in the domains configuration file: jms-system-resource namejmssysmod-jmsname targetcluster1,target sub-deployment nameservergroupname targetwlserver1,wlserver2,wlserver3target sub-deployment descriptor-file-namejmsjmssysmod-jms.xmldescriptor-file-name jms-system-resource Note: Changing the targets of a UDD can lead to the removal of a member destination and the unintentional loss of messages. Configuring Advanced JMS System Resources 4-13

4.5.2.2 Pausing and Resuming Message Operations on UDD Members