| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Configuring the queue manager alias |
« View previous topic :: View next topic » |
| Author |
Message
|
| jim |
 Posted: Fri Aug 08, 2014 7:03 am Post subject: Configuring the queue manager alias |
 |
|
Voyager
Joined: 26 Nov 2013
Posts: 94
|
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Fri Aug 08, 2014 9:14 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Non-clustering routing is essentially done via the Queue Manager name. On the 'Outside Qmgr' the definition
| Quote: |
| DEFINE QR(APP1.REMOTE) RNAME(APP.LOCAL) RQMNAME(PLANETSGW) XMITQ(MARS) |
means that any application putting to Q(APP1.REMOTE) will direct the message to PLANETSGW/APP.LOCAL and it will use transmission queue MARS to get there.
Presumably there is some channel defined to move message into the cluster that is reading transmission queue MARS.
When the message arrives in the 'Gateway QMgr' MQ will use normal queue resolution. To determine how to deal with the message. The message is targetted to PLANETSGW. Which clearly isn't the local QM name. So, MQ looks for a Queue Manger alias and finds this
| Quote: |
| DEFINE QR(PLANETSGW) RNAME(‘ ‘) RQMNAME(‘ ') |
So, this definition tells MQ to replace the PLANETSGW with a QM name of ' '(blanks). So, now the message is addressed to ' '/APP.LOCAL. Now, since the message is not now being addressed to a particular QM MQ will use normal Queue resolution to determine where to send it. Either a local queue or one somewhere in an available cluster. Assuming you have a set of APP.LOCAL definitions in your cluster the message will be sent, round-robin fashion, to one of the APP.LOCAL destinations.
Does that make sense? Or have I completely missed the point of your question ?
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Aug 08, 2014 9:26 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
The remote queue on the 'Outside Qmgr' explicitly puts messages on XMITQ MARS but addressed to Qmgr PLANETSGW. I will assume XMITQ MARS triggers a channel to 'Gateway Qmgr'. This is why the msg is routed to the 'Gateway Qmgr'. When the 'Gateway Qmgr' receives the msg it will see the QmgrAlias PLANETSGW and will clear (remap) the 'Addressed Qmgr' because the RQMNAME is blank and then try to resolve the target Queue name (either locally or from the cluster).
So that is use 1 and then 3. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Aug 08, 2014 12:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What might be a little bit confusing is that the manuals make little to no distinction between a qmgr alias and a cluster alias.
Both are remote queues used for routing messages.
In a qmgr alias you have rqmname populated and xmitq populated (if the next destination is not the local qmgr).
In a cluster alias rqmname and xmitq are blank (basically a qmgr alias for cluster use only)
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 08, 2014 12:59 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fjb_saper wrote: |
| What might be a little bit confusing is that the manuals make little to no distinction between a qmgr alias and a cluster alias. |
Neither of which have to do with using a QALIAS when working with AMS. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 08, 2014 1:16 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| fjb_saper wrote: |
| What might be a little bit confusing is that the manuals make little to no distinction between a qmgr alias and a cluster alias. |
There is little distinction to be made, really.
Whenever the qmgr encounters an object name, it attempts to resolve the name. If it can't resolve a name, you get one of those unknown or name_error ReasonCodes. If the name was typed correctly, then there is/was no object definition available that resolved the name.
To resolve a name, the qmgr first searches local definitions in this order: QLocal, QModel, QAlias, QRemote. If an object with a matching name is not found, the qmgr will next search the local cluster repository, then the full-repository.
When the need for qmgr aliases and cluster aliases arose, the folks at the mq factory decided to use a QRemote definition - without the RName attribute - instead of inventing another object type.
Please search here, or the Knowledge Center, for name resolution. For Luddites, find a .pdf or hardcopy of the WMQ Intercommunications manual, for a delightful, multi-page description of name resolution - with examples.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
