You have a dynamic application that can at anytime receive messages from
existing and NEW queue managers. Without overexcercising the ADMIN how would
you handle this. The request message itself will allow the application to
route the message back to the source without hardcoding queue names in the
program. Security is security and maybe this is an issue left for client
applications. But on an ITRANET I would think this is not an issue as
everyone should be trusted. Or are we coming down to the fact that you
cannot trust the person in the next cube! I implement this design when I
can. It makes design and functionality easier. If the client has a problem
with it . We just add 10 pounds of routing code to the program.
bobbee
From: Randy J Clark <[EMAIL PROTECTED]>
Reply-To: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Remote Queues
Date: Thu, 9 Jan 2003 13:49:50 -0800
I am asking for some opinions on sending to remote queues without having a
remote queue definition on the sending queue manager just specifying remote
qmgr and remote queue name in the MQOPEN.
Usig this method.
In the ObjectName field of the MQOD structure, specify the name of
the remote queue, as known to the remote queue manager. In the
ObjectQMgrName field, specify either:
The name of the transmission queue that has the same name as
the remote queue manager. Note that the name and case
(capitals, lower case or a mixture) must match exactly.
The name of a queue manager alias object that resolves to the
destination queue manager or the transmission queue.
This tells the queue manager the destination of the message as well
as the transmission queue it needs to be put on to get there.
I know there are or maybe times when you "have to" do it this way but
overall I am not crazy about the lack of documentation involved using this
method.
Seems to me even if the sending application is not going to create and use
a remote queue def on its own local Qmgr one should or maybe should exist
just for documentation purposes.
Without this it seems there is no reasonable way to know exactly what is
being sent between Qmgrs.
Any comments??
As you can tell I think there should be I know an extra object created even
if not used just for documentational purposes otherwise when ask what is
going between these two qmgrs I have no idea.
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
_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail
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
