Upgrade Guide › WebLogic Version › Upgrade on a WebLogic Cluster › How to Migrate a Cluster Installation to WebLogic 11 › Create a Distributed JMS Server for WebLogic

Create a Distributed JMS Server for WebLogic

To configure a WebLogic cluster for high availability, configure a distributed JMS server to manage queues and topics in JMS Modules for the cluster.

To create a distributed JMS server

1. Create an IM_JMS_filestore directory on the managed node. For example, on a Windows system:

   WL_HOME\user_projects\IM_JMS_filestore
   

2. Under Admin Console, go to Services, Messaging, JMS Servers, New JMS Server.
3. Configure the following JMS objects in the Persistent Store section:
   • JMS File Store

     Name: IM_JMS_filestore

     Directory: pathname/IM_JMS_filestore

   • JMS Server

     Server Name: jms_server_name (any meaningful name)

     Persistent Store: jms_store_name (the JMS File Store that you configured)

     Target: Set the target for these objects to the server where the JMS service will run. Use the imjmsmodule created during the installation.

     Note: The required distributed queues and topics were already created for use in the cluster during installation.

4. Repeat steps 1 through 3 for one managed node per server in the cluster.
5. Target GeneralMonitorCFdeployment subdeployment to each of the IM JMS servers you created. Associate GeneralMonitorCFdeployment with these resources:
   • GeneralMonitorCF
   • IMS Events
   • Run time status
   • Server Command Topic
   • General Monitor Messages

   Note: The cluster was used as a target of GeneralMonitorCFdeployment by the installer, so you need to remove it as a target.