Author |
Message
|
skrv |
Posted: Fri Oct 26, 2012 9:03 am Post subject: How to Write ReplyToQMgr field in the code in MQ API |
|
|
Centurion
Joined: 26 Oct 2012 Posts: 118
|
Hello,
Good Afternoon all.
We are having this issue where application team sending a Request message which has "ReplyToQ" and "ReplyToQMgr" fileds in message header, the message is reaching the destination queue manager but at the destination the application once grabbing this message, processing and while replying back, they don't know which/where to set the "ReplyToQMgr" field in the application code. hence they were not able to send the replies back.
Any suggestions in how/where to set this "ReplyToQMgr" field in the app code is much appreciated.
Application using MQ API.
thanks
skrv |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Oct 26, 2012 9:19 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Replying applications don't need to set reply-to-queue or reply-to-qmgr in the reply message. _________________ 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 |
|
 |
Vitor |
Posted: Fri Oct 26, 2012 9:20 am Post subject: Re: How to Write ReplyToQMgr field in the code in MQ API |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
skrv wrote: |
they don't know which/where to set the "ReplyToQMgr" field in the application code. hence they were not able to send the replies back. |
The obvious point is they shouldn't be trying to.
If they're trying to reply to a request, then they should using the values the requestor set in those fields. Because that's where the requestor wants the reply sent; the clue's in the name - ReplyTo.
Why does your design require the application sending the reply to deduce where it should be sent.
Which, for the record, is not achiveved by setting those fields. These are not used for routing a message and even if the replying application could figure out how to set them (which is in fact really obvious) it wouldn't help in getting the reply where it needs to go. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
skrv |
Posted: Fri Oct 26, 2012 9:33 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012 Posts: 118
|
Thanks for the quick reply.
They send request from app server end and message reached data zone, message is consumed by the application at datazone and need to send a reply back to app server from the details in Message header.
But for some reason application team may be not able to set "ReplyToQ" and "ReplyToQMgr" fileds in the request it self, so that they were not able to send replies back.
They are having issues in properly setting these filed in their code.
Below is the message from them:
---------------------------------------------------------------------------
"We have attempted to add the reply queue both as a message property "ReplyToQ" and programmatically setting JMSRerplyTo.
We are not seeing this property when receiving the message on the DATAZONE"
--------------------------------------------------------------------------- |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Oct 26, 2012 9:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
In the case of the requester, these are set on the MQMD.
In the case of the replier, these are set on the MQOD. |
|
Back to top |
|
 |
skrv |
Posted: Fri Oct 26, 2012 10:16 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012 Posts: 118
|
can you please give more details information on how to set it in MQOD? |
|
Back to top |
|
 |
skrv |
Posted: Fri Oct 26, 2012 10:19 am Post subject: |
|
|
Centurion
Joined: 26 Oct 2012 Posts: 118
|
one more thing we found out from application team is when they read message at DATAZONE they are only seeing the message content and not the message header information and it seems there is something wrong in the way they are reading the message. because when we capture that request message using q program we can see the message header details. But application team is not able to(not sure what they using to read it) and hence not able to reply dynamically and trying to set ReplyToQ and ReplyToQMgr filed again at DATAZONE end. |
|
Back to top |
|
 |
Vitor |
Posted: Fri Oct 26, 2012 10:47 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
skrv wrote: |
it seems there is something wrong in the way they are reading the message. |
You think?
skrv wrote: |
trying to set ReplyToQ and ReplyToQMgr filed again at DATAZONE end. |
As I said above & my most worthy associate confirmed, this will not help and will not route the message anywhere. The ReplyTo fields are in the MQMD, routing information is in the MQOD which must be in use or you can't send any message anyway (request, reply or datagram).
You'll find full details of this structure, and it's use, in the InfoCenter. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri Oct 26, 2012 11:12 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
A complete message is delivered to the consuming application. This includes MQMD and app data. This is basic mq. _________________ 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 |
|
 |
fjb_saper |
Posted: Sat Oct 27, 2012 3:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
And in case of JMS they are set on the Destination...  _________________ MQ & Broker admin |
|
Back to top |
|
 |
|