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

cd('/')
cmo.createJDBCStore('JDBCStore04')
cd('/JDBCStores/JDBCStore04')
cmo.setDataSource(getMBean('/JDBCSystemResources/ds-store'))
cmo.setPrefixName('JDBCStore04')
set('Targets',jarray.array([ObjectName('com.bea:Name=PROD_
Server04,Type=Server')], ObjectName))

activate()
exit()

See also

F Creating the JMS servers

Creating the JMS servers

The JMS server is a WebLogic resource that provides a container for the JMS queues and JMS
topics' destinations. A JMS server can manage several destinations at a time and it uses the
specified persistent store to persist the messages. The persistent store of the JMS server can
be the default persistent store of the WebLogic Server instance, a custom file store or a
JDBC store.

Following the roadmap configuration for the JMSApp application, a JMS server will be created
for each of the Managed Servers of the cluster PROD_Cluster , and each one will be
configured to use the file stores created before.

Getting ready

For the cluster PROD_Cluster , we will consider JMSServer01 , JMSServer02 ,
JMSServer03 , and JMSServer04 as the JMS Servers for instances PROD_Server01 ,
PROD_Server02 , PROD_Server03 , and PROD_Server04 respectively.

Each JMS server will use the custom file store created in the previous recipe. The JDBC stores
can also be used instead of the file stores.

Managed Server JMS server Persistent store

PROD_Server01 JMSServer01 FileStore01

PROD_Server02 JMSServer02 FileStore02

PROD_Server03 JMSServer03 FileStore03

PROD_Server04 JMSServer04 FileStore04