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

How it works...
The consumer operations can be temporarily paused through the Administration Console
when the JMS messages dequeue must stop in a situation of a maintenance window or
a troubleshooting process.
There's more...
JMS destinations can be controlled through WLST as well. This is discussed in the
following sections.
Pausing the consumers using WLST
This operation can be made by 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")
3. Run the following WLST commands:
domainRuntime()
cd('/ServerRuntimes/PROD_Server01/JMSRuntime/PROD_Server01.jms/
JMSServers/JMSServer01/Destinations/JMSAppModule!JMSServer01@
JmsAppQueue')
cmo.pauseConsumption()
cd('/ServerRuntimes/PROD_Server02/JMSRuntime/PROD_Server02.jms/
JMSServers/JMSServer02/Destinations/JMSAppModule!JMSServer02@
JmsAppQueue')
cmo.pauseConsumption()
cd('/ServerRuntimes/PROD_Server03/JMSRuntime/PROD_Server03.jms/
JMSServers/JMSServer03/Destinations/JMSAppModule!JMSServer03@
JmsAppQueue')
cmo.pauseConsumption()
cd('/ServerRuntimes/PROD_Server04/JMSRuntime/PROD_Server04.jms/
JMSServers/JMSServer04/Destinations/JMSAppModule!JMSServer04@
JmsAppQueue')
cmo.pauseConsumption()
exit()