How to connect two queue manager remotly

If you are in hurry to learn about remote connection between two queue managers then below are the simple practical steps which will help you to learn to connect to the geographically separate queue managers. This will also teach you to per-requisite and methodology involves.

Step- 1

Receiving queue manager

crtmqm qm.receiverqueuemanager

WebSphere MQ queue manager created.
Creating or replacing default objects for qm.receiverqueuemanager.
Default objects statistics: 40 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.

Step- 2

Sending Queue manager

crtmqm -q qm.senderqueuemanager

WebSphere MQ queue manager created.
Creating or replacing default objects for qm.senderqueuemanager.
Default objects statistics: 40 created. 0 replaced. 0 failed.
Completing setup.

 Step- 3

Start both the queue manager

strmqm qm.receiverqueuemanager

strmqm qm.senderqueuemanager

 Step -4

To create a listener in receiving queue manager i.e qm.receiverqueuemanager

runmqsc qm.receiverqueuemanager

define qlocal(q1)

end

Create a listener on qm.receiverqueuemanager

Runmqsc qm.receiverqueuemanager

define listener(qm.receiverqueuemanager.listener) trptype(TCP) port(30000)ipaddr(127.0.0.1)

start listener(qm.receiverqueuemanager.listener)

end

 Step- 5

Now time to crate listener at sender queue manage i.e. qm.senderqueuemanager

runmqsc qm.senderqueuemanager

define listener(qm.senderqueuemanager.listener) trptype(TCP) port(30001) ipaddr(127.0.0.1)

 start listener(qm.senderqueuemanager.listener)

We have all two queue manages created and listener created on them. Now create queues on them .

 Step -6

Create queue, transmission queues and remote queue definition on sender Queue manager i.e. qm.senderqueuemanager

runmqsc qm.senderqueuemanager

define qlocal (qm.senderqueuemanager.tq) usage(xmitq)

end

runmqsc qm.senderqueuemanager

define qremote(q1) rname(q1) rqmname(qm.receiverqueuemanager) xmitq(qm.senderqueuemanager.tq)

 end

we have to ensure that MQ explorer can connect to the queue managers, to do this we need to ensure that both queue managers have special channel created called SYSTEM.ADMIN.SVRCONN.

The server-connection channel, called SYSTEM.ADMIN.SVRCONN, must exist on every remote queue manager you need to manage using MQ explorer i.e. remote to the machine where you are running MQ Explorer. This channel is mandatory for every remote queue manager being administered by WebSphere MQ Explorer. Without it, remote administration is not possible.

runmqsc qm.receiverqueuemanager
5724-H72 (C) Copyright IBM Corp. 1994, 2005. ALL RIGHTS RESERVED.
Starting MQSC for queue manager qm.receiverqueuemanager.

DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
1 : DEFINE CHANNEL(SYSTEM.ADMIN.SVRCONN) CHLTYPE(SVRCONN)
AMQ8014: WebSphere MQ channel created.
start channel(SYSTEM.ADMIN.SVRCONN)
2 : start channel(SYSTEM.ADMIN.SVRCONN)
AMQ8018: Start WebSphere MQ channel accepted.
end
3 : end
2 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.

Step -7

What we have to do is create a channel objects to allow the queue managers to connect to each other. We need a channel object at each end of the channel one will be a sender object and one will be a receiver object.

Create channel on sender queue manager

runmqsc qm.senderqueuemanager

define channel (qm.senderqueuemanager.qm.receiverqueuemanager) chltype (sdr) conname (‘192.168.0.60(30000)’) xmitq (qm.senderqueuemanager.tq) trptype (tcp)

 Step -8

What we need to do now is create a receiving channel object on qm.receiverqueuemanager

runmqsc qm.receiverqueuemanager

define channel (qm.senderqueuemanager.qm.receiverqueuemanager) chltype (RCVR) trptype (TCP)