|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Local Queue Redirection |
« View previous topic :: View next topic » |
Author |
Message
|
k9i |
Posted: Sun Jul 11, 2004 2:44 pm Post subject: Local Queue Redirection |
|
|
Newbie
Joined: 11 Jul 2004 Posts: 8
|
In an attempt to split administration rights, I would like to have two queue managers collocated on a single server. One queue manager is to be dedicated to application interaction (where application developers/administrators may manage queues during developent/testing) and the other queue manager dedicated for WBIMB (lets call them QM_APP and QM_WBRK). The plan is to later establish more queue managers for different application areas. The goal is to have messages sent to an application queue (e.g. APPQ1 on QM_APP) forwarded to a queue named WBRKQ1 on QM_WBRK for input to a WBIMB message flow.
The question (problem) that I have is how to configure a "remote" queue in QM_APP that forwards to a local queue in QM_WBRK on the *same machine*. I have attempted two configurations. The first was to setup a remote queue (APPQ1) defined with the broker queue name (WBRKQ1) and the queue manager set to QM_WBRK only. The second attempt was create a setup with channel and transmit queues like the mult-server examples in the MQ documentation - but all on the same host. When I use a setup that does not include a transmission queue/channel, I get an MQRC_UNKNOWN_REMOTE_Q_MGR error. When I try to setup transmission queue/recieve channels between the two queue managers, I get configuration errors because the channel names clash. I've been through the Intercommunication, System Adminstration and Cluster doc and could not find a comparable configuration. Also - can I put both of these queue managers in the same cluster?
Thanks!
-R |
|
Back to top |
|
 |
PeterPotkay |
Posted: Sun Jul 11, 2004 5:26 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Quote: |
The first was to setup a remote queue (APPQ1) defined with the broker queue name (WBRKQ1) and the queue manager set to QM_WBRK only.
.
.
.
When I try to setup transmission queue/recieve channels between the two queue managers, I get configuration errors because the channel names clash.
|
Without channels between them, QMs cannot exchange messages, so option 1 will never work. Option 2 is the way to go.
Assume your server is called Server1.
QM_APP listens on port 1414.
QM_WBRK listens on port 1415.
On QM_APP, define a SNDR channel called QM_APP.QM_WBRK, on its conname parameter will say Server1(1415). Also create a RCVR channel called QM_WBRK.QM_APP.
On QM_WBRK, define a SNDR channel called QM_WBRK.QM_APP, on its conname parameter will say Server1(1414). Also create a RCVR channel called QM_APP.QM_WBRK.
Quote: |
The plan is to later establish more queue managers for different application areas.
|
Don't get carried away with that. 10 QMs each hosting 10 queues uses alot more resources than 1 QM hosting 100 queues, plus there is a heck of a lot more admin work to do, although clustering will aleviate that somewhat.
Quote: |
Also - can I put both of these queue managers in the same cluster?
|
Sure. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|