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

How it works...
The SAF agent and SAF resources were configured in PROD_DOMAIN to forward messages
to the jms.remotequeue queue hosted by the REMOTE_DOMAIN domain. The JNDI
representation of the jms.remotequeue queue in the PROD_DOMAIN domain is jms.
remotequeue-saf .
The SAF agent was configured to use the persistent stores FileStore01 , FileStore02 ,
FileStore03 , and FileStore04 to persist the messages.
With this configuration, every message posted to the jms.remotequeue-saf agent
from the PROD_DOMAIN domain is forwarded to the jms.remotequeue queue of the
REMOTE_DOMAIN domain.
There's more...
The SAF agent and resources can be configured using WLST.
Configuring the SAF agents and SAF resources using WLST
This change can be made 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. Create the SAF agents by running the following WLST commands:
edit()
startEdit()
cd('/')
cmo.createSAFAgent('SAFAgent_01')
cd('/SAFAgents/SAFAgent_01')
cmo.setStore(getMBean('/FileStores/FileStore01'))
set('Targets',jarray.array([ObjectName('com.bea:Name=PROD_
Server01,Type=Server')], ObjectName))
cmo.setServiceType('Sending-only')
cd('/')