| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MsgId and CorrId Mapping Issues |
« View previous topic :: View next topic » |
| Author |
Message
|
| rajmq |
 Posted: Wed May 07, 2003 9:03 am Post subject: MsgId and CorrId Mapping Issues |
 |
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
As per our bussines requirement I need to do below implementation:
1.Client System is sending msg to our Host
the message which is having unique msgid and corrId,
while sending back the response msg i am setting same msgId and CorrId.So the Client able to ready response msg.
2Now the problem is the same scenario i was trying with Wmqi2.1 Pub/Sub
My ControlCenter is having msg flow like...
MQInputNode------------->ComputNode---------->PublicationNode
After getting the host response i am passing the message to MQInputNode,Using the Compute node properties i am publishing the msg and client has received the same message.But the problem is the client is excepting the same msgId and CorrId.I checked the client log the msgId and CorrId are differnt.
MyComputeNode Properities:
SET OutputRoot.MQMD = InputRoot.MQMD;
SET OutputRoot.MQRFH2.psc.Command = 'Publish' ;
SET OutputRoot.MQRFH2.psc.Topic = 'XXXXXX' ;
SET OutputRoot.MQMD.msgId = InputRoot.MQMD.msgId;
SET OutputRoot.MQMD.corrId = InputRoot.MQMD.corrId
SET OutputRoot.XML = InputRoot.XML;
Can anyone tell me where i am doing wrong?? or
Is it possible to set same MsgId and CorrId using the Pub/Sub Concepts??
regards
raj |
|
| Back to top |
|
 |
| puvvada |
| Posted: Tue May 13, 2003 1:31 pm Post subject: Re:MsgId and CorrId Mapping Issues |
|
|
Apprentice
Joined: 01 Apr 2002
Posts: 27
|
Hi Raj,
Even I had the same issue before during pub/sub. We developed a custom node to log MsgId of every message that flows through the Broker, so that we can map the MsgId at the receiveing application. This works fine with normal message flows but we got different MsgId for pub/sub flows. Since the messages are published by the broker, it creates its own MsgId. I looked at other options and I couldn't figure it out.
I think, we both are on the same boat.
Let me know if you were able to find any alternate solution.
Thanks
-Deven |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue May 13, 2003 1:49 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
As far as I know, and you can only do what you want for the CorrelId and only when you specify CorrelAsId in the registration options. The message Id will always be unique.
From the programming guide:
| Quote: |
MQMD for publications forwarded by a broker
This section describes the message descriptor for messages sent by the broker to
subscribers.
...
MsgId Will be set to a unique value.
CorrelId If CorrelId is part of the subscriber’s identity, this is the value
specified by the subscriber when registering. Otherwise, it is a
non-zero value chosen by the broker.
... |
|
|
| Back to top |
|
|
| rajmq |
| Posted: Wed May 14, 2003 1:07 am Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
Thanks to all
I got the information from IBM. Using the Pub/Sub scenario we can't assign same msgId and CorrlId.Be'z broker is handling that part,For that they sugessted Request/Reply scenario using ReplyNode.
I planning to use the IBM suggestion....
regards
raj |
|
| 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
|
|
|
|
