| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Debugging FanOut and FanIn flows |
« View previous topic :: View next topic » |
| Author |
Message
|
| chris boehnke |
 Posted: Tue Jun 05, 2007 1:25 pm Post subject: Debugging FanOut and FanIn flows |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi,
I am trying to debug the FanOut(request to web services) and FanIn(reply from web services).
I am able to debug the FanOut flow by setting some breakpoints inside the flow.
When I debug the FanIn flow, there are 2 messages coming(reply message from web + Echo message from FanOut, which is original message) and adding in Aggregate Reply node. When the 2 messages are adding in the Aggregate Reply node, I dont see any further movement of the message in debugging mode after the Aggregate Reply node. How to debug the FanIn flow properly?. Any suggestions????
Thanks.
Chris |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Tue Jun 05, 2007 8:46 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
After the aggregation node in the fan in flow you need a compute node to really put together the different messages as presented on the aggregation.
This is the node you put your breakpoint in.
Now if you need to truely debug the work the aggregation is doing this is an other matter entirely.
I would suggest at this point that you make sure your output is correct:
a) no correlId on the message sent to the services requested. It is understood by those services that if the correlId is empty it uses the messageId as correlId.
b) make sure that each outgoing message(fan out) has its own messageId.
c) make sure the replyto information includes the queue the qmgr is waitin
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Wed Jun 06, 2007 8:44 am Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| fjb_saper wrote: |
After the aggregation node in the fan in flow you need a compute node to really put together the different messages as presented on the aggregation.
This is the node you put your breakpoint in.
Now if you need to truely debug the work the aggregation is doing this is an other matter entirely.
I would suggest at this point that you make sure your output is correct:
a) no correlId on the message sent to the services requested. It is understood by those services that if the correlId is empty it uses the messageId as correlId.
b) make sure that each outgoing message(fan out) has its own messageId.
c) make sure the replyto information includes the queue the qmgr is waitin
Enjoy |
Hi,
I am using the break points in FanIn flow in a Compute node just after the Aggregate Reply node.
I am using the XSLTs in converting the Mainframe Cobol message to XML.
While debugging the FanIn flow, I dont see the queue name in Replytoq field. Where we are setting this field?..
With the old cobol copybook and old input message, the flow is working fine and I can see the replytoq field with the queue name.
Now I have a new requirement in which I am using a new message and new cobol copybook(messageset). With this new requirement, when I debug the flow, I dont see the replytoq field. Please suggest how and where we are setting this field.
Still I am using the old XSLTs...do you think that could be the reason???
Thanks |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Wed Jun 06, 2007 9:21 am Post subject: |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
| chris boehnke wrote: |
| fjb_saper wrote: |
After the aggregation node in the fan in flow you need a compute node to really put together the different messages as presented on the aggregation.
This is the node you put your breakpoint in.
Now if you need to truely debug the work the aggregation is doing this is an other matter entirely.
I would suggest at this point that you make sure your output is correct:
a) no correlId on the message sent to the services requested. It is understood by those services that if the correlId is empty it uses the messageId as correlId.
b) make sure that each outgoing message(fan out) has its own messageId.
c) make sure the replyto information includes the queue the qmgr is waitin
Enjoy |
Hi,
I am using the break points in FanIn flow in a Compute node just after the Aggregate Reply node.
I am using the XSLTs in converting the Mainframe Cobol message to XML.
While debugging the FanIn flow, I dont see the queue name in Replytoq field. Where we are setting this field?..
With the old cobol copybook and old input message, the flow is working fine and I can see the replytoq field with the queue name.
Now I have a new requirement in which I am using a new message and new cobol copybook(messageset). With this new requirement, when I debug the flow, I dont see the replytoq field. Please suggest how and where we are setting this field.
Still I am using the old XSLTs...do you think that could be the reason???
Thanks |
I AM SORRY...It was my mistake. I was trying to place the message through Rfhutil and I forgot to provide the reply queue name in Rfhutil...
Thanks. |
|
| 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
|
|
|
|
