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

cd('/')
cmo.createJMSSystemResource('JMSAppModule')
cd('/JMSSystemResources/JMSAppModule')
set('Targets',jarray.array([ObjectName('com.bea:Name=PROD_
Cluster,Type=Cluster')], ObjectName))
activate()
exit()
See also
F Creating the JMS servers
F Configuring the subdeployment targeting
Configuring the subdeployment target
The JMS module JMSAppModule is targeted to the cluster PROD_Cluster , meaning the
JMS resources added to the module will use the PROD_Cluster cluster as the default target.
Because of the JMS resource, such as a distributed queue, the default target is not the best
option for production.
WebLogic Server has a feature called subdeployment targeting to handle this special
targeting. The subdeployment allows a JMS resource to use a different target from the default
JMS module target, using a single or multiple WebLogic Server instances, WebLogic clusters,
or JMS servers as target.
Subdeployment is a not a precise term and confuses WebLogic
administrators. Subdeployment is better referred to as advanced
targeting.
In this recipe a new subdeployment called JMSAppSub will be created targeting only the JMS
servers created for the JMSApp application.
Getting ready
The subdeployment JMSAppSub will be created using the Administration Console.
Make sure the Administration Server is running and the JMSAppModule module
is created.