| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| invalid replyId on reply message for Aggregation |
« View previous topic :: View next topic » |
| Author |
Message
|
| jagan |
 Posted: Mon Oct 15, 2007 8:44 am Post subject: Re: Invalid replyId on reply message for Aggregation |
 |
|
Acolyte
Joined: 26 Jun 2001
Posts: 55
|
| fjb_saper wrote: |
| jagan wrote: |
Hi,
Our SOA initiative was on hold, so we kept out Aggregation project pending. Now we got a green signal so keep this post back to active..
fjb_saper, I have tried with your the option but no luck..
SET OutputRoot.MQMD.Format = MQFMT_STRING;
EddieA, answering to your question and trying explain the senario:
Flow1: Getting one HTTP request, which contains number of records. So get this request from my first flow, i am diving into each record adding the MQ header and placing it into MQ Queue.
Flow2: Get the message from MQ, and then pass the message to a webserice, once the response comeback and the MQ header (Adding it again because Webservice response wont have the MQ Header) again and placing it into MQReply.
Flow3: This is Simple one, but getting the Invalid Reply ID error...
I Know iam missing some thing here, but i have used all my options.. If requires i will send the code, please let me know if any of you have done Aggregation examples using HTTP request and HTTP response..
Thanks
Jagan |
Not getting a clear picture here.
How are you storing / restoring your MQMD?
Are you passing it from one flow to the other? how? 
You are aware that in an aggregation (if you use multiple flows) you should pass the original MQM if needed as payload of an additional aggregation request? |
FLow1: Creating the MQMD structure and placing it on the queue.
Flow2: Get the message and store the MQMD before calling a webserive, once recieving the response adding the MQMD stucture(which was copied before) and putting it on the MQReply node.
| Quote: |
| You are aware that in an aggregation (if you use multiple flows) you should pass the original MQM if needed as payload of an additional aggregation request? |
Iam not getting the above statement  |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon Oct 15, 2007 8:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay, let's start with the basics.
The Aggregation nodes are only really useful in the following situation:
A single message must be turned into multiple ASYNCHRONOUS requests, and the responses to those requests must be combined to form a single response to the original single message.
If all of your outbound requests are HTTP, then they are all synchronous, and not only does Aggregation not give you any value, it is not necessary and only causes Aggravation.
You can wire your flow like:
HTTPInput->Compute--(loop)-->HTTPRequest--(end loop)-->Compute-->HTTPReply
Where you are looping over as many outbound requests as you need. You just need to ensure that you are configuring the HTTPRequest node to put the response message somewhere other than as the full output message.
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/topic/com.ibm.etools.mft.doc/ac04595_.htm
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
