The Queue name I push when we a developing infrastructure is SendingApp.ReceivingApp.AnythingYouWant
Channels are generic-ly Sender.Receiver with variations considered for multiple QMGRS on the same box and testing cyclye (eg SandBox, Dev, SIT, UAT, QA, Prod, DR)
bobbee
From: [EMAIL PROTECTED] Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: Questionable MQ infrastructure design Date: Sun, 13 Jul 2003 18:01:36 +1000
Hi,
We have a similar name scheme for channels except much shorter.... SRC_DST and optionallyPROD_SRC_DST, not by application though.
For queues,we normally use a qualifier on the end of the queue name/type for the type of data i.e.
ie app_type.pgp (PGP encrypted data) app_type_subtype.xml
etc
Same goes for Transmission queues and initiation queues
app_process.initq app_process.txq
I think you can see the pattern..
Sid
-----Original Message----- From: Armand ten Dam [mailto:[EMAIL PROTECTED] Sent: Thursday, 10 July 2003 10:58 AM To: [EMAIL PROTECTED] Subject: Questionable MQ infrastructure design
Hi all, For an integration project I have been asked to adopt an MQ naming standard that reflects a very unusual approach in MQ-based integration. I have never seen this approach before and have serious concerns in adopting any of it.
Key in the design is the use of separate queue managers for each application pair. E.g. if an application interfaces with eight different distributed applications this would result in eight separate queue managers on a single system.
Some examples: Queue manager: QMPROD.SOURCECOMPANY.SOURCEAPP.TARGETCOMPANY.TARGETAPP.SYSTEMNAME Channel: CHPROD.SOURCECOMPANY.SOURCEAPP.TO.TARGETCOMPANY.TARGETAPP Transmission queue: TXPROD.SOURCECOMPANY.SOURCEAPP.TO.TARGETCOMPANY.TARGETAPP ...
Obviously this does not reflect best-practice, seriously impacts scalability, makes support of the MQ infrastructure difficult etc.
As it looks like it will be a bit of a political discussion to get this out of the way, I am looking to gather as much 'neutral' feedback to back me up. I would appreciate it if some of you could shed some more light on the implications of the above approach.
Any insights much appreciated, Thanks, Armand
_________________________________________________________________ Hot chart ringtones and polyphonics. Go to http://ninemsn.com.au/share/redir/adTrack.asp?mode=click&clientID=174&referr al=Hotmail_taglines_plain&URL=http://ninemsn.com.au/mobilemania/default.asp
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
_________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
