Author |
Message
|
lillo |
Posted: Mon Feb 28, 2005 12:01 am Post subject: Aggregate control node |
|
|
Master
Joined: 11 Sep 2001 Posts: 224
|
I searched in the forum about the question I saw others had the same question.
I am developing a fan-out message flow with aggregate control node and I can't see the control message. I tried with the debugger and also with a trace node and couldn't see any output.
is there any change in the node behaviour since the migration to 5.0? I am running 5.0 CSD3.
BRs, _________________ Lillo
IBM Certified Specialist - WebSphere MQ |
|
Back to top |
|
 |
Nizam |
Posted: Mon Feb 28, 2005 7:25 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004 Posts: 160
|
lillo,
Did you specify the aggregate name and the timeout for the aggreagate control node?
I am using aggregate nodes and I can see the message after it passes the aggregate control node.
It is an xml message with timeout etc.,
Aslo use a compute after your aggregate control node to copy the inputroot to outputroot. |
|
Back to top |
|
 |
JT |
Posted: Mon Feb 28, 2005 7:31 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
In v5.0 the aggregate control information is stored in LocalEnvironment.ComIbmAggregateControlNode, I believe that's the same location as v2.1. So the ${LocalEnvironment} trace pattern should display the control information.
As you may know, you can also use a queue as an intermediary between the AggregateControl node and the AggregateReply node. Using a destinationlist, and adding a second queue, stores a copy of the control information where you should be able to view it.
If the AggregateReply node is not receiving the control information, are you modifying the LocalEnvironment tree in the compute node, and forgetting to add the following line of ESQL code:
Code: |
SET OutputLocalEnvironment.ComIbmAggregateControlNode =
InputLocalEnvironment.ComIbmAggregateControlNode; |
|
|
Back to top |
|
 |
Nizam |
Posted: Mon Feb 28, 2005 7:36 am Post subject: |
|
|
Disciple
Joined: 10 Feb 2004 Posts: 160
|
JT,
I just verified and found that the control information is sent in the message area and did not find anything in the LocalEnvironment.
You are right but I do not know why I am seeing this. But my flows work fine.
Nyzam |
|
Back to top |
|
 |
lillo |
Posted: Mon Feb 28, 2005 7:42 am Post subject: |
|
|
Master
Joined: 11 Sep 2001 Posts: 224
|
JT wrote: |
In v5.0 the aggregate control information is stored in LocalEnvironment.ComIbmAggregateControlNode, I believe that's the same location as v2.1. So the ${LocalEnvironment} trace pattern should display the control information.
|
You are refering here to the normal path in the fan-out message, but I refered to the control terminal in the aggregatecontrol node.
Nizam wrote: |
Did you specify the aggregate name and the timeout for the aggreagate control node?
I am using aggregate nodes and I can see the message after it passes the aggregate control node.
It is an xml message with timeout etc.,
Aslo use a compute after your aggregate control node to copy the inputroot to outputroot. |
Yes, I specified both. I only particular thing in the message flow is that the aggregatecontrol node is in a subflow where the aggregate name is promoted.
I also but a trace node connected to the control terminal and nothing was in the trace file. _________________ Lillo
IBM Certified Specialist - WebSphere MQ |
|
Back to top |
|
 |
lillo |
Posted: Mon Feb 28, 2005 7:44 am Post subject: |
|
|
Master
Joined: 11 Sep 2001 Posts: 224
|
Nizam wrote: |
JT,
I just verified and found that the control information is sent in the message area and did not find anything in the LocalEnvironment.
You are right but I do not know why I am seeing this. But my flows work fine.
Nyzam |
You are talking about what you get after the aggregate control node, but you refered to the different terminals. Nizam refers to the control terminal, as I do, and JT refers to the out terminal. _________________ Lillo
IBM Certified Specialist - WebSphere MQ |
|
Back to top |
|
 |
JT |
Posted: Mon Feb 28, 2005 7:44 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003 Posts: 1564 Location: Hartford, CT.
|
My recollection was a little fuzzy, so I looked it up and you are correct. The LocalEnvironment tree is used as follows:
Quote: |
The AggregateControl node inserts elements into the LocalEnvironment tree in the input message that the AggregateRequest node reads when the message reaches it. |
|
|
Back to top |
|
 |
|