Home >Documents >Basic MQ Queue Manager Cluster

Basic MQ Queue Manager Cluster

Date post:03-Mar-2015
Category:
View:298 times
Download:8 times
Share this document with a friend
Transcript:

IBM Software Group

WebSphere MQ Basic Queue Manager ClustersTim Elwood WebSphere MQ Level 2 Customer Support

WebSphere Support Technical Exchange

IBM Software Group

Agenda Terminology Benefits How queue manager clusters work Setting up a basic MQ cluster Display commands What's new in WebSphere MQ V7.0 Troubleshooting Tips References

WebSphere Support Technical Exchange

2 of 40

IBM Software Group

Terminology Cluster - A cluster is a network of queue managers that arelogically associated in some way

Cluster queue manager - A cluster queue manager is aqueue manager that is a member of a cluster

Cluster queue A cluster queue is a queue that is hosted bya cluster queue manager and made available to other queue managers in the cluster

Repository A repository is a collection of information aboutthe queue managers that are members of a cluster

WebSphere Support Technical Exchange

3 of 40

IBM Software Group

Terminology - cont. 1 Repository queue manager A repository queue manager is acluster queue manager that holds a full repository

Full repository A queue manager that hosts a complete set ofinformation about every queue manager in the cluster is referred to as having a full repository for the cluster.

Partial repository is a queue manager that contains partial setof cluster information that includes knowledge about full repositories as well as other partial repository that it previously interacted with.

WebSphere Support Technical Exchange

4 of 40

IBM Software Group

Terminology - cont. 2 Cluster-receiver channel A cluster-receiver (CLUSRCVR)channel definition provides the receiving end of a channel on which a cluster queue manager can receive messages from other queue managers in the cluster

Cluster-sender channel A cluster-sender (CLUSSDR)channel definition provides the sending end of a channel on which a cluster queue manager can send cluster information as well as application messages to other clustered queue managers.

WebSphere Support Technical Exchange

5 of 40

IBM Software Group

Terminology - cont. 3 SYSTEM.CLUSTER.TRANSMIT.QUEUE is used totransmit cluster and application messages.

SYSTEM.CLUSTER.COMMAND.QUEUE is used toprocess internal cluster information messages.

SYSTEM.CLUSTER.REPOSITORY.QUEUE is used tostore cluster information.

WebSphere Support Technical Exchange

6 of 40

IBM Software Group

Cluster Overview

WebSphere Support Technical Exchange

7 of 40

IBM Software Group

BenefitsThere are two reasons for using clusters: 1. Reduced system administration. A network of queue managers in a cluster involves fewer definitions Set up or change your network more quickly and easily with fewer definitions to make, and reduce the risk of making an error in your definitions. 2. Increased availability and workload balancing. Easier system administration Improved scalability workload can be distributed

WebSphere Support Technical Exchange

8 of 40

IBM Software Group

How queue manager clusters work? Figure 7: A cluster of queue managers, showing manual andauto-defined channels

WebSphere Support Technical Exchange

9 of 40

IBM Software Group

How queue manager clusters work? cont. 1 AMQRRMFA is the repository manager processwhich governs all cluster activity for a queue manager.

Every cluster has at least one (preferably two)

queue managers holding full repositories of information about the queue managers, queues, and channels in a cluster

WebSphere Support Technical Exchange

10 of 40

IBM Software Group

How queue manager clusters work? cont. 2 Queue managers need a cluster-receiver and acluster-sender channel definitions in order to join a cluster.

Each queue manager that joins a cluster will need tohave a manually defined cluster-sender (CLUSSDR) channel to one of the full repositories.

A full repository is updated when it receives newinformation from a queue manager that is trying to join a cluster.WebSphere Support Technical Exchange 11 of 40

IBM Software Group

How queue manager clusters work? cont. 3 Queue managers build up their partial repositoriesby making inquiries to full repository when they first need to access another queue or queue manager within a cluster.

Based on the information that a queue managerreceives from a full repository, it automatically creates a cluster-sender channel to the partial repository to send data across.

WebSphere Support Technical Exchange

12 of 40

IBM Software Group

How queue manager clusters work? cont. 4 Full repository queue managers will each need tohave manually defined cluster sender and cluster receiver channels made on the full repository queue managers

These channels are used exclusively by the fullrepositories to send user data as well as resync cluster information to reflect changes in the cluster.

WebSphere Support Technical Exchange

13 of 40

IBM Software Group

Setting up a basic MQ cluster Figure 5: The INVENTORY cluster with two queue managers

WebSphere Support Technical Exchange

14 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 1 Decide on the organization of the cluster and itsname Determine which queue managers should hold full repositories Alter the queue-manager definitions to add repository definitions ALTER QMGR REPOS(INVENTORY) AMQ8005: Websphere MQ queue manager changed.

WebSphere Support Technical Exchange

15 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 2 Define the CLUSRCVR channelsDEFINE CHANNEL(TO.LONDON) CHLTYPE(CLUSRCVR) TRPTYPE(TCP) CONNAME(LONDON.CHSTORE.COM) CLUSTER(INVENTORY) DESCR(TCP Cluster-receiver channel for queue manager LONDON) AMQ8014: Websphere MQ channel created. 07/09/98 12:56:35 No repositories for cluster INVENTORY

WebSphere Support Technical Exchange

16 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 3 Define the CLUSSDR channelsDEFINE CHANNEL(TO.NEWYORK) CHLTYPE(CLUSSDR) TRPTYPE(TCP) CONNAME(NEWYORK.CHSTORE.COM) CLUSTER(INVENTORY) DESCR(TCP Cluster-sender channel from LONDON to repository at NEWYORK) AMQ8014: Websphere MQ channel created. 07/09/98 13:00:18 Channel program started.

WebSphere Support Technical Exchange

17 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 4 Define the cluster queueDEFINE QLOCAL(INVENTQ) CLUSTER(INVENTORY) AMQ8006: Websphere MQ queue created. The CLUSTER keyword causes the queue to be advertised to the cluster. As soon as the queue is defined it becomes available to the other queue managers in the cluster. Messages can be sent without having to make a remote-queue definition

WebSphere Support Technical Exchange

18 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 5 Verify and test the clusterdis clusqmgr(*) AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(NEWYORK) CLUSTER(INVENTORY) CHANNEL(TO.NEWYORK) AMQ8441: Display Cluster Queue Manager details. CLUSQMGR(LONDON) CLUSTER(INVENTORY) CHANNEL(TO.LONDON)

WebSphere Support Technical Exchange

19 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 6 DISPLAY CHANNEL STATUS command: dis chstatus(*) AMQ8417: Display Channel Status details. CHANNEL(TO.NEWYORK) XMITQ( ) CONNAME(9.20.40.24) CURRENT CHLTYPE(CLUSRCVR) STATUS(RUNNING) RQMNAME(LONDON) AMQ8417: Display Channel Status details. CHANNEL(TO.LONDON) XMITQ(SYSTEM.CLUSTER.TRANSMIT.QUEUE) CONNAME(9.20.51.25) CURRENT CHLTYPE(CLUSSDR) STATUS(RUNNING) RQMNAME(LONDON)WebSphere Support Technical Exchange 20 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 7 amqsput sample program within MQ used to put samplemessages amqsget sample program within MQ used to get sample messages On LONDON issue the command: amqsput INVENTQ LONDON. Type some messages 3. On NEW YORK issue the command: amqsget INVENTQ NEW YORK. You should now see the messages you entered on LONDONWebSphere Support Technical Exchange 21 of 40

IBM Software Group

Setting up a basic MQ cluster - cont. 8 Define a cluster queue.DEFINE QLOCAL(INVENTQ) CLUSTER(INVENTORY)

Other queue managers in the cluster can sendmessage to it without making remote-queue definitions for it.

You can only GET from a local cluster queue, butyou can PUT to any queue in a cluster.

WebSphere Support Technical Exchange

22 of 40

IBM Software Group

Multiple full repositories Multiple full repositories require that each fullrepository has a manually defined cluster sender channel to every other full repository in the cluster

WebSphere Support Technical Exchange

23 of 40

IBM Software Group

Display Commands DISPLAY QUEUE(*) CLUSINFO DISPLAY QCLUSTER(*) ALLDisplay Queue details. to display information about clustered queues

DISPLAY CHSTATUS(*) ALL

Display Channel Status details. Display Cluster Queue Manager details. Display Queue Manager details.

DISPLAY CLUSQMGR(*) ALL

DISPLAY QMGR REPOS REPOSNL QMID DISPLAY CLUSQMGR(qm name) DISPLAY CHSTATUS(channel name)To see the auto-defined channels

WebSphere Support Technical Exchange

24 of 40

IBM Software Group

Clustered Topics new in WebSphere MQ V7.0 MQ cluster topics are MQ objects thatidentifies what a publication is about.

When you define a cluster topic, the clustertopic is published to the