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

cmo.setPersistentStore(getMBean('/JDBCStores/JDBCStore03'))
set('Targets',jarray.array([ObjectName('com.bea:Name=PROD_
Server03,Type=Server')], ObjectName))
cd('/')
cmo.createJMSServer('JMSServer04')
cd('/JMSServers/JMSServer04')
cmo.setPersistentStore(getMBean('/JDBCStores/JDBCStore04'))
set('Targets',jarray.array([ObjectName('com.bea:Name=PROD_
Server04,Type=Server')], ObjectName))
activate()
exit()
See also
F Creating the file stores
F Creating the JDBC stores
F Creating the JMS module
Creating the JMS module
The JMS module is a WebLogic global system resource that aggregates and stores JMS
resources and JMS-related configurations such as queues, topics, connection factories,
quotas, distributed queues, and distributed topics.
There are two types of JMS modules: the JMS application module and the JMS system
module. In this recipe, the JMS system module will be covered since it is the module WebLogic
administrators use for creation and configuration. Although it has the same functions as those
of a system module, the JMS application module should be handled by the developer and has
to be included and packaged inside the application's EAR file.
The system module is also preferred over the application module because the application
module can be handled only by manually editing the XML. The system module, on the other
hand, can be managed through the Administration Console, WLST, or JMX.
Continuing the setup process for the JMS resources needed by the JMSApp application,
create a new JMS module called JMSAppModule in PROD_DOMAIN .