Configuring JMS Resources for Clustering and High Availability - Oracle WebLogic Server 12c Advanced Administration - page 123

3. Run the following WLST commands:
edit()
startEdit()
cmo.createSubDeployment('JMSAppSub')
cd('/JMSSystemResources/JMSAppModule/SubDeployments/JMSAppSub')
set('Targets',jarray.array([ObjectName('com.bea:Name=JMSServer
01,Type=JMSServer'), ObjectName('com.bea:Name=JMSServer02,Type
=JMSServer'), ObjectName('com.bea:Name=JMSServer03,Type=JMSSer
ver'), ObjectName('com.bea:Name=JMSServer04,Type=JMSServer')],
ObjectName))
activate()
exit()
See also
F Creating the JMS servers
F Creating the distributed queue destination and the connection factory
Creating the distributed queue destination
and the connection factory
Oracle WebLogic Server 12 c has two types of queues: the queue and the distributed queue.
The queue is a JMS resource targeted to a single Managed Server.
A distributed queue must be used when working with WebLogic clustering. The distributed
queue is a logical entity that groups single queues distributed across the JMS servers and
Managed Servers of the cluster but is accessible as a single and transparent JNDI name. JMS
applications require that all resource and JNDI names be unique across the entire application
environment, including the WebLogic domains involved, the clusters, Managed Servers, and
JMS resources.
The members (queues) of the distributed queue can use weighted or uniform distribution.
Use the uniformly distributed queue for JMS clustering. The weighted
distribution is more complicated to create and manage and it is
deprecated in WebLogic Server 12 c .