| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Queue Names |
« View previous topic :: View next topic » |
| Author |
Message
|
| omhopper |
 Posted: Mon Sep 08, 2008 2:17 pm Post subject: Queue Names |
 |
|
Novice
Joined: 08 Jun 2007
Posts: 17
|
I just had a lengthy discussion about queue naming with one of our developers. We use the best practices I've seen many times, i.e. all caps, no spaces, short as possible but still descriptive. The part we couldn't agree on though was from http://www.ibm.com/developerworks/websphere/library/techarticles/0807_hsieh/0807_hsieh.html.
"Applications should have a high-level qualifier consisting of a few characters, followed by some delimiter (like a dot), so that the names sort easily and the purpose of the queue is obvious (such as APPXYZ.SERVICE1.REQUEST)."
Our standard in the above case has always been that APPXYZ is the application accepting the request to do "something" ... the provider. The developer wanted me to name the queue based on the calling application, or requester.
Which way has worked best for you? Any help on why?
_________________
Thanks. |
|
| Back to top |
|
 |
| atheek |
| Posted: Mon Sep 08, 2008 2:38 pm Post subject: |
|
|
Partisan
Joined: 01 Jun 2006
Posts: 327
Location: Sydney
|
| We used to name APPXYZ.SERVICE1.REQUEST as the name of the receiver local queue and the remote queue at sender side as something like REQUESTER.SERVICE1.APPXYZ.REQUEST. It looks logical to name the receiver queue based on its name as it can service multiple requesters |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Sep 08, 2008 2:41 pm Post subject: Re: Queue Names |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| omhopper wrote: |
I just had a lengthy discussion about queue naming with one of our developers. We use the best practices I've seen many times, i.e. all caps, no spaces, short as possible but still descriptive. The part we couldn't agree on though was from http://www.ibm.com/developerworks/websphere/library/techarticles/0807_hsieh/0807_hsieh.html.
"Applications should have a high-level qualifier consisting of a few characters, followed by some delimiter (like a dot), so that the names sort easily and the purpose of the queue is obvious (such as APPXYZ.SERVICE1.REQUEST)."
Our standard in the above case has always been that APPXYZ is the application accepting the request to do "something" ... the provider. The developer wanted me to name the queue based on the calling application, or requester.
Which way has worked best for you? Any help on why? |
This is one of the areas where it becomes logical to use QAlias.
It is easy to set the authorization patterns for MYAPP.** and not have to worry. That the base Qname underneath might be MYSVCE.** should not matter.
The apps would now be authorized on whether they have an alias pointing to the service's base queue.
As an alternative you can also specifically authorize the app's user grp to access the MYSVCE.** pattern... but these are really considerations of the user and where the admin feels more confident. 
_________________
MQ & Broker admin
Last edited by fjb_saper on Mon Sep 08, 2008 8:27 pm; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Sep 08, 2008 3:27 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
It's a guideline that works for most applications. Guidelines usually are generic in nature.
For example, queues associated with a payroll application should/could be prefixed with PAY. followed by the queue function, like PAY.TIMECARD. This differentiates PAY. queues from AP. (accounts payable) queues and FIN. (financial) queus.
Naming a queue after the the application program that puts messages into it might not survive the intended purpose if some other application in the future ends up putting messages in the same queue.
Guidelines also suggest not naming a queue for its location or the undelying o/s or the server/node name.
_________________
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 |
|
|
| omhopper |
| Posted: Mon Sep 08, 2008 3:53 pm Post subject: |
|
|
Novice
Joined: 08 Jun 2007
Posts: 17
|
Thanks. The quote from Bruce is the one I dropped on him.
"Naming a queue after the the application program that puts messages into it might not survive the intended purpose if some other application in the future ends up putting messages in the same queue."
[/quote]
_________________
Thanks. |
|
| 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
|
|
|
|
