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

6. Click and enable only the checkboxes JMSServer01 , JMSServer02 , JMSServer03 ,
and JMSServer04 and click on the Finish button.
7. Click on the Activate Changes button to finish.
How it works...
The subdeployment JMSAppSub was created for the JMS module JMSAppModule , pointing
to the JMS servers JMSServer01 , JMSServer02 , JMSServer03 , and JMSServer04 ,
meaning that any JMS resource targeting to the subdeployment will be restricted for use by
the selected JMS servers only.
In the next recipe, the JMS resources required by the JMSApp application will be configured
to target the subdeployment JMSAppModule .
There's more...
The subdeployment can also be created with WLST.
Configuring the subdeployment using WLST
1. Log in as a wls user to the shell and start WLST:
[wls@prod01]$ $WL_HOME/common/bin/wlst.sh
2. Connect to the Administration Server using wlsadmin as user, <pwd> as the
password, and t3://adminhost.domain.local:7001 as the server URL.
wls:/offline>connect("wlsadmin","<pwd>","t3://adminhost.domain.
local:7001")