Configuring V5 releases to access MQ Cluster Queues
 Technote (troubleshooting)
 
Problem(Abstract)
When configuring WebSphere® Application Server V5 releases to connect to a WebSphere MQ queue that is part of a queue cluster, messages can be delivered only to one of the queues in the cluster. How can WebSphere Application Server be configured so that messages are distributed between all queues in the cluster?
 
Cause
Detailed instructions for configuring WebSphere Application Server to distribute a message to all the queues in a cluster.
 
Resolving the problem
There are two changes that must be made to the WebSphere MQ Queue Destination within WebSphere Application Server. Select the Queue Destination in the WebSphere Application Server Administrative Console, then make the following changes:
  • Clear the Base Queue Manager Name field. If there is a Queue Manager name in this field, all messages are sent to that Queue Manager.
  • Click MQ Config under Additional Properties. Find the Default Binding property. By default it is set to On Open. It should be changed to Not Fixed for the messages to be sent to all queues in the cluster. You can also use the WebSphere MQ administration tools to change the Default Binding.

After making these changes, save the configuration and restart the Application Server. Now messages are distributed between all queues in the cluster.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1162745
IBM Group: Software Group
Modified date: Mar 9, 2004