| Author |
Message
|
| doubt_master |
 Posted: Fri Jul 13, 2007 11:22 am Post subject: AggregateReplyNode |
 |
|
Novice
Joined: 02 Mar 2007
Posts: 10
|
I have an interesting question regarding AggregateReplyNode.
Whenever messages that arrive at Unknown terminal of AggregateReplyNode the message tree
is collapsing and if use a compute before it and saving the reply message in
environment variables then also the environment variables is vanishing from the tree.
Which is the better way of regaining the original message at the unknown terminal. |
|
| Back to top |
|
 |
| wbi_telecom |
| Posted: Fri Jul 13, 2007 11:56 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
| Quote: |
Whenever messages that arrive at Unknown terminal of AggregateReplyNode the message tree
is collapsing
|
What exactly happens ? Do you get any errors?
| Quote: |
if use a compute before it and saving the reply message in
environment variables then also the environment variables is vanishing from the tree.
|
Can you share the esql ?
Cheers, |
|
| Back to top |
|
|
| doubt_master |
| Posted: Fri Jul 13, 2007 12:15 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2007
Posts: 10
|
CREATE COMPUTE MODULE StoreData
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
SET OutputRoot.Properties.MessageSet= 'A3056S002003;
SET OutputRoot.Properties.MessageType= 'Envelope';
SET OutputRoot.Properties.MessageFormat= 'XML1';
SET OutputRoot.MQMD= InputRoot.MQMD;
SET OutputRoot.MQRFH2= InputRoot.MQRFH2;
SET Environment.Variables.MQMD= InputRoot.MQMD;
SET Environment.Variables.MQRFH2= InputRoot.MQRFH2;
SET OutputRoot.MRM = InputRoot.MRM;
RETURN TRUE;
END;
This code if before the compute node of AggregateReplyNode .
If the message goes to unknown there will be no MRM or ExceptionList tree created. |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Jul 13, 2007 12:27 pm Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
If the objective is to preserve the MQMD, here's what we do. We send the MQMD as a separate message to a queue in the Fan out message flow and collect it back in the Fan in message flow. We convert MQMD to BLOB and then get it back using CREATE and PARSE.
Cheers, |
|
| Back to top |
|
|
| doubt_master |
| Posted: Fri Jul 13, 2007 12:44 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2007
Posts: 10
|
Thanks for your valuable information.
What is my requirement is to recover the whole message when it is timeout |
|
| Back to top |
|
|
| doubt_master |
| Posted: Fri Jul 13, 2007 12:45 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2007
Posts: 10
|
sorry i want to correct my question.
Actually in my first post please replace unknown terminal with timout terminal |
|
| Back to top |
|
|
| wbi_telecom |
| Posted: Fri Jul 13, 2007 12:59 pm Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
I am confused. The message goes to Timeout node when all the replies for a request are not received with the timeout interval specified. So can you trace the message that you are getting at the Timeout terminal before you start copying the InputRoot to OutputRoot because it may not have all the folders and you may have to create some in order to put it on a queue successfully.
Cheers, |
|
| Back to top |
|
|
|
|
