But sometimes the reply *MUST* come back to the broker that sent it, so I can't use a solution that eliminates that possibility.
Wayne Shutz on mqseries.net suggested ReplyTo Aliases, which I suppose will work (see below), but I wish there was a better way, i.e. allowing the flow to easily and quickly check environmental stuff so that it can act accordingly. *********************** BROKERA and BROKERB are in CLUSTER1. REPLYQ is the real reply q. I would have to define this: DEFINE QREMOTE(REPLYQ.ALIAS) RNAME(REPLYQ) RQMNAME(CLUSTER1) And then the flow would specify REPLYQ.ALIAS for the MQMD.ReplyToQueue. When the message left, it would be tagged in the MQMD with ReplyToQueue = REPLYQ and ReplyToQueueManager = CLUSTER. Cool. Hmmmm, yeah, I guess that will work. All it means is for every reply queue on my brokers, I would then have to create a replyto alias. (That's alot of queues, but what the hay) If the flow wants the reply to come back to the cluster, it sets the reply to queue to REPLY.ALIAS, and if it wants it to come back to the specific broker, then it just codes the actual reply queue (REPLYQ) in that field. Man, I wish there was a better way. Someone at work suggested creating a queue on each Broker called WHO.AM.I, and putting a persistent message with unlimited Expiry that would contain pertinent info, like the broker name. Any flow that wanted to know the info would use the MQGET node to open that queue, and get the message. Then they would have to roll it back, or put a copy of it back on the queue. Probably would perform like a dog, and if the message gets eaten for good and not replaced, we are sunk. ************************************* -Peter -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Michael Dag Sent: Wednesday, July 20, 2005 5:45 PM To: [email protected] Subject: Re: What cluster am I in? Peter, >From what I recall you work with Gateway Queuemanager(s) to access the cluster, so I assume that your replies get back to the cluster only always end up on the same queue manager the broker sent the message from... What you need to do on the Gateway Queuemanager(s) is define X (=number of Clustered broker Qmgrs) QMAlias definitions that not only have a blank RNAME but also have a blank RQMNAME and XMITQ This will make sure the original queuemanager name that was in the MQMD get's BLANKED and so you can let clustering do it's work... So if you have 2 broker QMGRS called QMBRK1 and QMBRK2 Define on your gateway(s) (that ARE part of the cluster) a QMALIAS definition with blank RNAME, RQMNAME and XMITQ ! Michael -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Potkay, Peter M (ISD, IT) Sent: woensdag 20 juli 2005 23:23 To: [email protected] Subject: Re: What cluster am I in? It makes sense, and my Reply queues are clustered, but the Replier could be inside or outside the cluster. If they are outside, (95% of the time) they will need to populate the Destination QM value with the cluster name so my QMAliases will catch the reply message and route it back to the cluster. -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Michael Dag Sent: Wednesday, July 20, 2005 5:15 PM To: [email protected] Subject: Re: What cluster am I in? Peter, It's not about the cluster it's about the Queue, Make sure the replyToQueue is clustered and the Path back to the cluster is known. Make sure to Set the reply to QM to BLANK. Clustering will see which Queue is available and Put the message there through round robin, your Broker need not do anything special. It's late so I hope this made sense... Michael -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Potkay, Peter M (ISD, IT) Sent: woensdag 20 juli 2005 23:06 To: [email protected] Subject: What cluster am I in? With 2 or more brokers in the same MQ cluster, I would like to have the outgoing Request flow produce a message whose Reply To QM field contains the name of the MQ Cluster, so that when the reply message comes back, it can go to any of my brokers, and not be obligated to going back to the Broker that processed the request. Since the Cluster names change between LAB, DEV, QA and PROD, I need a way for the flow to find out what environment it is in, so that it can dynamically set the MQMD_ReplyToQManager field to the proper cluster name depending on what environment it is in. Any ideas? > Peter Potkay > ISD MQSeries Support Manager > The Hartford Financial Services > [EMAIL PROTECTED] > x77906 > IBM MQSeries Certified > ************************************************************************* PRIVILEGED AND CONFIDENTIAL: This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. ************************************************************************* Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
