This example describes how to create a cluster solution with a server complex (INTERNAL and EXTERNAL) and a fault tolerant input system which utilize simple workload balancing. Yes, there are a single point of failure in this configuration, there are only one customer Queue Manager, but it's not relevant for this scenario.
QMA1 and QMA3 acts as "Gateway" Queue Managers, and they are hosting full repositories for all four clusters. Here is a sample screen shot from QMA3 using explorer showing the queues.
and as you can see, all your queues and your customers queues are shown on QMA1 and QMA3 (because QMA1 and QMA3 are hosting both your and your customers repository), good or not ?
QMA2 and QMA4 acts as server Queue Managers hosting the server queues (PUBLISHED.QUEUE and INTERNAL.QUEUE) , which offers workload balancing (default based on round robin). All QALIAS' are defined DEFBIND(NOTFIXED), otherwise this configuration won't work.
QME1 is a "Customer" Queue Manager, which is joined to the cluster, but it can only see the queues published by QMA1 and QMA3 in this case (PUBLIC.QUEUE). Below is a sample screen shoot showing QME1 Queues
And as you can see is there only the published queues available to the customer.
Here is a full overview of the configuration of them, queues, channels and so, all presented by MQ-Inventory®. Complete overview of the QMA-cluster.
Download the full stanza for the configuration and some sample screen shots here.
The following are trademarks of
International Business Machines Corporation:
IBM, MERVA, MQSeries, WebSphere, WFNI, Object REXX