Scribd
Upload
148 views2 pages

Clustering

The document describes the steps to set up a cluster between two queue managers, QM1 and QM2, called CLUS. The steps include deciding on the cluster name and organization, designating which queue managers will hold full repositories, altering queue manager definitions to add repository attributes, defining cluster receiver and sender channels, and defining a cluster queue called SampleQ. The setup is then verified using DISPLAY commands and by sending test messages between the queue managers.

Uploaded by

chlaxmikanth
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
148 views2 pages

Clustering

The document describes the steps to set up a cluster between two queue managers, QM1 and QM2, called CLUS. The steps include deciding on the cluster name and organization, designating which queue managers will hold full repositories, altering queue manager definitions to add repository attributes, defining cluster receiver and sender channels, and defining a cluster queue called SampleQ. The setup is then verified using DISPLAY commands and by sending test messages between the queue managers.

Uploaded by

chlaxmikanth
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Setting up a new Cluster

The two queue managers, QM1 and QM2 are to be linked in a cluster called CLUS so
that they can both put messages to the SampleQ.

The steps required to complete task

To set up this cluster, follow these steps.

1. Decide on the organization of the cluster and its name


You have decided to link the two queue managers, QM1 and QM2 into a cluster. The
cluster name is CLUS.

2. Determine which queue managers should hold full repositories


In any cluster you need to nominate at least one queue manager, or preferably two, to
hold full repositories. In this example there are only two queue managers, QM1 and
QM2, both of which hold full repositories.

3. Alter the queue-manager definitions to add repository definitions


On each queue manager that is to hold a full repository, you need to alter the
queue-manager definition, using the ALTER QMGR command and specifying the
REPOS attribute:
4.Define the CLUSRCVR channels
On every queue manager in a cluster you need to define a cluster-receiver channel
on which the queue manager can receive messages.
On the QM1 queue manager, define:
On the QM2 queue manager, define:
5. Define the CLUSSDR channels
On every queue manager in a cluster you need to define one cluster-sender channel on
which the queue manager can send messages to one of the full repository queue
managers. In this case there are only two queue managers, both of which hold full
repositories. They must each have a CLUSSDR definition that points to the CLUSRCVR
channel defined at the other queue manager.

On the QM1queue manager, define:


On the QM2 queue manager, define:

6. Define the cluster queue SampleQ

Define the SampleQ queue on the QM2 queue manager, specifying the CLUSTER
keyword.
Verifying task

Issue some DISPLAY commands to verify the cluster that you have set up. The responses
you see should be similar to those shown in the examples that follow.

From the QM2 queue manager, issue the command:


dis clusqmgr (*)

Now issue the corresponding DISPLAY CHANNEL STATUS command:


dis chstatus (*)

Test your setup by sending some messages between the two queue managers, using
amqsput. In the following example QM1 puts a message to the SampleQ at QM2:
1. On QM1 issue the command:
AMQSPUT SampleQ QM1

2. Type some messages

3. On QM2 issue the command:


AMQSGET SampleQ QM2

4. You should now see the messages you entered on QM1.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy