| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue and Channel Naming Conventions............ |
« View previous topic :: View next topic » |
| Author |
Message
|
| vivek.gargMQ |
 Posted: Mon Dec 18, 2006 3:47 am Post subject: Queue and Channel Naming Conventions............ |
 |
|
Novice
Joined: 12 Oct 2006
Posts: 19
|
Our Queue Name will be according to Queue Name Matrix and QM and Channels according to specified naming conventions in EAI doc.
According to that convention, I tried to create these.
QM1 – LNIAD01
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QR
Local Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QL
Trans Queue – LNI.LNIAD01
Sender Channel – LNI.LNIAD01.LNIAD02
QM2 – LNIAD02
Local Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QL
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QR
Trans Queue – LNI.LNIAD02
Receiver Channel – LNI.LNIAD01.LNIAD02
Error according to convention………………..
Channel is not starting If I follow above convention.
Previously in our testing we follow a convention, under it, This will run perfectly fine.
1) Remote Queue in QM1 will same as of Local Queue in QM2 for Request Message.
2) Remote Queue in QM2 will same as of Local Queue in QM1 for Reply Message.
3) Sender Channel in QM1 will same as of and Receiver Channel of QM2.
4) Sender Channel in QM2 will also be same as Receiver Channel of QM1. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 18, 2006 3:50 am Post subject: Re: Queue and Channel Naming Conventions............ |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| vivek.gargMQ wrote: |
Channel is not starting If I follow above convention.
|
With what error?
What steps have you already taken in an attempt to resolve this?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Dec 18, 2006 4:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Have you looked at creating additional remote queues to satisfy the default transmission requirements (see intercommunications manual ==> queue manager alias)?
| Code: |
| def qr(lniad02) rqmname(lniad02) xmitq(lni.lniad01) |
You will need to remember that as the conventions outlined in your post are fine they do not follow MQ conventions.
Looking at channel names MQ conventions are:
Max length of channel name = 20 char
point to point: <QM1>.TO.<QM2>, <QM1>.<QM2>,
cluster: TO.<QM2>
Now of course you can replace QM1 or QM2 with anything and it does not HAVE to be a qmgr name....
But remember that if you want automatic routing you'll need either the xmitq to be the qmgr name or a qmgr alias or a cluster...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Tue Dec 19, 2006 12:18 am Post subject: Re: Queue and Channel Naming Conventions............ |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
| vivek.gargMQ wrote: |
Our Queue Name will be according to Queue Name Matrix and QM and Channels according to specified naming conventions in EAI doc.
According to that convention, I tried to create these.
QM1 – LNIAD01
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QR
Local Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QL
Trans Queue – LNI.LNIAD01
Sender Channel – LNI.LNIAD01.LNIAD02
QM2 – LNIAD02
Local Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QL
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QR
Trans Queue – LNI.LNIAD02
Receiver Channel – LNI.LNIAD01.LNIAD02
Error according to convention………………..
Channel is not starting If I follow above convention.
Previously in our testing we follow a convention, under it, This will run perfectly fine.
1) Remote Queue in QM1 will same as of Local Queue in QM2 for Request Message.
2) Remote Queue in QM2 will same as of Local Queue in QM1 for Reply Message.
3) Sender Channel in QM1 will same as of and Receiver Channel of QM2.
4) Sender Channel in QM2 will also be same as Receiver Channel of QM1. |
I guess LNI is some sort of application specific queue name prefix !?!
Then you should not use the same prefix for the XmitQs, because XmitQs belong to the channel and to the topology of your MQ network - not to any specific application. I would also remove the additional prefix in the channel names, because you already mentioned the application shortcut in the name of the QMgrs. Channel names are limited to 20 characters, and you may need some more characters in the future, to distinguish between different channel types (online or batch, non-SSL or SSL ...).
It is useful, to name a transmission queue like the target queue manager. In your sample I would use the following conventions:
| Quote: |
...
QM1 – LNIAD01
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QR
Local Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QL
Trans Queue – LNIAD02
Sender Channel – LNIAD01.LNIAD02
QM2 – LNIAD02
Local Queue - LNI.ORION.CLM_MODULE_UPDT.PUB.QL
Remote Queue - LNI.ORION.CLM_MODULE_UPDT.SUB.QR
Trans Queue – LNIAD01
Receiver Channel – LNIAD01.LNIAD02
... |
_________________
Regards
Hubert |
|
| 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
|
|
|
|
