Setting up a new cluster
Follow these instructions to set up the example cluster. Separate instructions describe setting up the cluster on TCP/IP, LU 6.2, and with a single transmission queue or multiple transmission queues. Test the cluster works by sending a message from one queue manager to the other.
Before you begin
- Instead of following these instructions, you can use one of the wizards supplied with MQ Explorer to create a cluster like the one created by this task. Right-click the Queue Manager Clusters folder, then click , and follow the instructions given in the wizard.
- For background information to aid your understanding of the steps taken to set up a cluster, see Defining cluster queues, Cluster channels and Listeners.
About this task
You are setting up a new IBM® MQ network for a chain store. The store has two branches, one in London and one in New York. The data and applications for each store are hosted by systems running separate queue managers. The two queue managers are called LONDON
and NEWYORK
. The inventory application runs on the system in New York, connected to queue manager NEWYORK
. The application is driven by the arrival of messages on the INVENTQ
queue, hosted by NEWYORK
. The two queue managers, LONDON
and NEWYORK
, are to be linked in a cluster called INVENTORY
so that they can both put messages to the INVENTQ
.
Figure 1 shows what this cluster looks like.
You can configure each queue manager in the cluster to send messages to other queue managers in the cluster using different cluster transmission queues.
The instructions to set up the cluster vary a little by transport protocol , number of transmission queues, or platform. You have a choice of three combinations. The verification procedure remains the same for all combinations.
Procedure
- Setting up a cluster using TCP/IP with a single transmission queue per queue manager
- Setting up a cluster on TCP/IP using multiple transmission queues per queue manager
- Setting up a cluster using LU 6.2 on z/OS
- Verifying the cluster
Results
Figure 1 shows the INVENTORY
cluster setup by this task.
Clearly, INVENTORY
is a small cluster. However, it is useful as a proof of concept. The important thing to understand about this cluster is the scope it offers for future enhancement.
Setting up a cluster using TCP/IP with a single transmission queue per queue manager
Before you begin
- The queue manager attribute, DEFCLXQ, must be left as its default value, SCTQ.
About this task
Follow these steps to set up a cluster on AIX®, HP-UX, IBM i, Linux®, Solaris, and Windows using the transport protocol TCP/IP. On z/OS®, you must follow the instructions in Defining a TCP connection on z/OS to set up the TCP/IP connection , rather than defining the listeners in step 4. Otherwise, the steps are the same for z/OS, but error messages are written to the console, rather than to the queue manager error log.
Procedure
Setting up a cluster on TCP/IP using multiple transmission queues per queue manager
About this task
Procedure
Setting up a cluster using LU 6.2 on z/OS
Procedure
Verifying the cluster
About this task
- Running administrative commands to display cluster and channel attributes.
- Run the sample programs to send and receive messages on a cluster queue.
- Write your own programs to send a request message to a cluster queue and reply with a response messages to an non-clustered reply queue.
Procedure
Issue DISPLAY
runmqsc commands to verify the cluster.
The responses you see ought to be like the responses in the steps that follow.
Send messages between the two queue managers, using amqsput.
Send messages between the two queue managers using your own programs.
In the
following steps, LONDON
puts a message to the INVENTQ
at
NEWYORK
and receives a reply on its queue
LONDON_reply
.