Task 7: Adding a new, interconnected cluster
Notes:
- For changes to a cluster to be propagated throughout the cluster, at least
one full repository must always be available. Ensure that your repositories
are available before starting this task.
- Before starting this task the system administrators of the two clusters
must check for queue-name clashes and be sure that they understand the consequences.
You might need to rename a queue, or perhaps set up queue aliases before you
can proceed.
Scenario:
- A WebSphere MQ cluster has been set up as described in Task 6: Converting an existing network into a cluster.
- A new cluster called MAILORDER is to be implemented. This cluster will
comprise four of the queue managers that are in the CHAINSTORE cluster; CHICAGO,
CHIGACO2, SEATTLE, and ATLANTA, and two additional queue managers; HARTFORD
and OMAHA. The MAILORDER application will run on the system at Omaha, connected
to queue manager OMAHA. It will be driven by the other queue managers in the
cluster putting messages on the MORDERQ queue.
- The full repositories for the MAILORDER cluster will be maintained on
the two queue managers CHICAGO and CHICAGO2.
- The network protocol is TCP.