Defining components of a cluster
Clusters are composed of queue managers, cluster channels, and cluster queues. We can define cluster queues, and modify some aspects of default cluster objects. We can get configuration and status information about auto-defined channels, and about the relationship between individual cluster-sender channels and transmission queues.
See the following subtopics for information about defining each of the cluster components:
Defining cluster queues
A cluster queue is a queue that is hosted by a cluster queue manager and made available to other queue managers in the cluster.Define a cluster queue as a local queue on the cluster queue manager where the queue is hosted. Specify the name of the cluster the queue belongs to.
Working with auto-defined cluster-sender channels
After you introduce a queue manager to a cluster by making its initial CLUSSDR and CLUSRCVR definitions, IBM MQ automatically makes other cluster-sender channel definitions when they are needed. We can view information about auto-defined cluster-sender channels, but we cannot modify them. To modify their behavior, we can use a channel auto-definition exit.
Working with default cluster objects
We can alter the default channel definitions in the same way as any other channel definition, by running MQSC or PCF commands. Do not alter the default queue definitions, except for SYSTEM.CLUSTER.HISTORY.QUEUE.
Working with cluster transmission queues and cluster-sender channels
Messages between clustered queue managers are stored on cluster transmission queues and forwarded by cluster-sender channels. At any point in time, a cluster-sender channel is associated with one transmission queue. If you change the configuration of the channel, it might switch to a different transmission queue next time it starts. The processing of this switch is automated, and transactional.
Parent topic: Configure a queue manager cluster
Related tasks
Related information