WebLogic Clustered Queues

Clustered Queue

  • Create new domain for your cluster using config.cmd in (common\bin).
  • Choose a name and location for your domain and start the admin server.
  • Copy newly created domain folder to other machines where you want to deploy the cluster.
  • On the machines where you copied the domain you must also configure the node manager so that it knows about the new domain. The machine where the domain was created is automatically updated with the right info through the config.cmd command. You need to make sure that the domain is listed in nodemanager.domains file (common\nodemanager). If you don’t see a nodemanager.properties file just copy it from the machine where you created the domain.
  • Start the node manager (from the Weblogic start menu) on all machines participating in the cluster.
  • Connect to the admin server and create a Machine for each computer in the cluster (Environment->Machines).
  • After creating the machines edit their configuration and update their node manager configurations so that they point to their respective node managers. It is recommended that you use their external hostnames (i.e. podxxxx).
  • Now create a new server (aka Managed Server) and specify the hostname/port of the machine where the server is going to live.
  • Modify the configuration of the server so that the server targets the appropriate machine (Environment->Servers->YOUR SERVER).
  • From the Servers section select the control tab and start your server to verify your servers configuration.
  • Stop the server(s) (not the admin server).
  • Repeat the previous steps to create as many new servers on the machines as you need.
  • Create a new Cluster (Environment->Cluster) and name the cluster, leave the other fields default.
  • From the cluster page select your cluster, then select the servers tab and add your servers to the cluster.
  • Create your JMS servers (Services->Messaging->JMS Servers).
  • Choose a name and which managed server the JMS server is associated with (pick migratable if you need failure tolerance).
  • Create your JMS Module (Services->Messaging->JMS Modules), pick a name (leave other fields default) click next and select your JMS cluster.
  • Click next and then select to create a Resource for your JMS module.
  • Click new and the select distributed queue.
  • Pick a name and JNDI name for your distributed queue and click finish.
  • Select the Subdeployments tab, click new and pick a name for your subdeployment.
  • Verify that the queue is hooked up right (JMS Module->YOUR MODULE->YOUR RESOURCE->Monitoring Tab).
  • When connecting to the queue from your java app set the provider URL (java.naming.provider.url) to something like “t3://ip:port,ip:port” for each server/port in your cluster

Other Notes

From Weblogic documentation:

If you define the cluster address as a DNS name, the Listen Ports for the cluster members are not specified in the cluster address it is assumed that each Managed Server in the cluster has the same Listen Port number. Because each server instance in a cluster must have a unique combination of address and Listen Port, if a cluster address is a DNS name, each of the server instance in the cluster must have: * a unique address and * the same Listen Port number

It's only fair to share...
Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Leave a Reply