Home

 

Organizing a cluster

 

Having selected the queue managers to hold full repositories, we need to decide which queue managers should link to which full repository. The CLUSSDR channel definition links a queue manager to a full repository from which it finds out about the other full repositories in the cluster. From then on, the queue manager sends messages to any two full repositories, but it always tries to use the one to which it has a CLUSSDR channel definition first. It is not significant which full repository you choose. However, you should consider the topology of your configuration, and perhaps the physical or geographical location of the queue managers as shown in Figure 1 through Figure 3.

Queue managers on WebSphere MQ V6 z/OS support PCF commands, so the MQ Explorer can use them to query information about the cluster (in just the same way as with distributed queue managers). However z/OS queue managers up to WebSphere MQ v5.3.1 do not support PCF commands so the MQ Explorer cannot use them to query information about the cluster. For this reason the MQ Explorer does not allow you to select WebSphere MQ v5.3.1 z/OS queue managers at the source of the information about a cluster.

Because all cluster information is sent to two full repositories, there might be situations in which you want to make a second CLUSSDR channel definition. You might do this in a cluster that has a large number of full repositories, spread over a wide area, to control which full repositories your information is sent to.

 

Parent topic:

Designing clusters

qc11240_

 

Home