|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Retrieve CorrelId / MsgId from MQOutput- Message Broker |
« View previous topic :: View next topic » |
Author |
Message
|
upcominggeek |
Posted: Tue Aug 05, 2008 7:03 am Post subject: Retrieve CorrelId / MsgId from MQOutput- Message Broker |
|
|
 Apprentice
Joined: 21 Aug 2006 Posts: 35 Location: Boston, US
|
Hi,
I have a flow listening on SOAPInput and need to send an MQ message.
Interestingly, even though I check the option to generate a new MsgId /
CorrelId in the MQOutput Node of Message Broker, the values appears as
X'000...0' for both of them when I access MQMD after the MQOutput Node.
But both of them have non-zero values in the actual message put to the
queue. Seems like Broker is not passing them in MQMD after the MQOutput
node. Any pointers?
Any other tips to uniquely generate CorrelIds that can be accessed
within the flow is also welcome.
And also, the written destination list value for MsgId/CorrelId
(retrieved after MQOutput) is different from the MQMD value of the
actual MQ message. Any idea why?
I did look into other posts which discuss correlid issues. But could not find a solution that will work for me.
Thanks,
UpcomingGeek |
|
Back to top |
|
 |
helenw |
Posted: Tue Aug 05, 2008 8:42 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2008 Posts: 1
|
Output nodes do not change their input when they pass hte message to the out terminal. As you have noted the MQMD values for Message Id or Correl ID remain zero. However the written destination does contain the correct generated message ID. I have certainly used this to retrieve by correlId in a later MQGET node so that I can store away information (such as the Soap ReplyID and get it back when I get the MQ response in another flow.
The SOAP reply only works if both flows are in the same execution group. |
|
Back to top |
|
 |
upcominggeek |
Posted: Tue Aug 05, 2008 9:17 am Post subject: Problem solved |
|
|
 Apprentice
Joined: 21 Aug 2006 Posts: 35 Location: Boston, US
|
Yes, you are right. Writtendestinationlist contains the correct MsgId/CorrelId. There was a bug in the code because of which the msgid value in the final message was coming differently from the writtendestinationlist. |
|
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
|
|
|
|