| Author |
Message
|
| zpat |
 Posted: Thu Jul 14, 2011 10:33 am Post subject: |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Collector node is WMB v7 only though. The version of WMB wasn't stated. But it does sound like it makes it much easier.
How do you signal the collector node that you have finished? |
|
| Back to top |
|
 |
| Sai K |
| Posted: Thu Jul 14, 2011 10:46 am Post subject: |
|
|
Novice
Joined: 23 Jun 2011
Posts: 22
|
I configured the collector node as...
In Basic tab: Terminal : message
Quantity : 5
Timeout: 0
Correlation Path: $Root/MQMD/CorrelId
Before the collector node, I put compute node. In that compute node i pu the below code:
SET OutputRoot.MQMD.CorrelId = InputRoot.MQMD.GroupId;
I created the input terminal for collector node as Message. But once it passed the collector node,it is taking terminal as control.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 14, 2011 10:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| Collector node is WMB v7 only though. |
Really? It's a bit lucky that not only did I accidently get shipped a copy of v6.1 media with the node included, they put instructions for it in the v6.1 InfoCenter..... 
| zpat wrote: |
| How do you signal the collector node that you have finished? |
In the example quoted here there are 2 methods I can see. You can either use the MQInput to read only completed groups and assume everything that turns up inside a time period (like the 120 second wait on your MQGet solution) is part of the same collection.
A better solution is to use the fact all the associated messages have the same account number (or group id) and have the Collector group those together.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 14, 2011 10:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sai K wrote: |
I configured the collector node as...
In Basic tab: Terminal : message
Quantity : 5
Timeout: 0
Correlation Path: $Root/MQMD/CorrelId |
Why? How can you know you have 5 messages to read? In 0 seconds?
And what's the advantages of copying the id to the correlation id rather than using it in situ? Why do that?
| Sai K wrote: |
| I created the input terminal for collector node as Message. But once it passed the collector node,it is taking terminal as control.. |
Once what passed the Collector node? What are you seeing taking the terminal as the control? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sai K |
| Posted: Thu Jul 14, 2011 11:12 am Post subject: |
|
|
Novice
Joined: 23 Jun 2011
Posts: 22
|
| I just tried a sample with the 5 messages and a sample value in timeout. I am not seeing the XMLNSC populated in the message. Am i doing any thing wrong. Please suggest me the need ful . Thanks in advance. |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jul 14, 2011 11:19 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
"All available messages" means only the flow starts only when the entire message group is on the queue - no need to wait in this case. It's not a very clear description.
6.1 - new fangled. We've just bought extended support for 6.0... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 14, 2011 11:46 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sai K wrote: |
| I am not seeing the XMLNSC populated in the message. |
Where are you looking? I hope it's not directly under the Root where the XMLNSC normally is.
| Sai K wrote: |
| Am i doing any thing wrong. |
Apparently. But as I can't see how you've got your flows wired up, your queues configured, where you think the control terminal fits into this or what test data you're using it's hard to really comment.
| Sai K wrote: |
| Please suggest me the need ful. |
Make sure you've properly read and understood how the Collector node works. Pay especial attention to how it assembles collections, the effect each of the parameters has and how it presents the assembled collection to the rest of the flow.
Do not just drop it into the flow,set some likely sounding values and think it will work. It won't.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Jul 14, 2011 12:36 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
In one of my previous posts in this thread I pointed you in the direction of the solution to your problem of understanding the output from a collectornode.
viz, put a trace node connected to the output of the collector. Define the trce pattern to be ${Root}
DISCONNECT THE DEBUGGER
enable user trace and put a group of messages on the input queue
extract the trace (mqsireadlog) and format it(mqsiformatlog).
You will see the format of the data in all its glory.
It is not like a normal XMLNSC message structure. It can't be because a single messafe tree has to handle multiple structures.
I wish more people would use user trace. It can often be more helpful in understanding what is going on inside a flow.
 (brickwall meet head)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 14, 2011 12:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| smdavies99 wrote: |
| I wish more people would use user trace. It can often be more helpful in understanding what is going on inside a flow. |
But what can you do? We live in an age of visual tools 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Sai K |
| Posted: Fri Jul 15, 2011 6:33 pm Post subject: |
|
|
Novice
Joined: 23 Jun 2011
Posts: 22
|
I developed the flow with collector node and I can able to generate email.
I designed flow like mqinput --> collector --> compute-- > email.
In compute node, I am looping the collection result set, take the account number and generate on email..
Victor..I really appreciate your thought of collector node.
Thanks for all your input.. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Jul 15, 2011 11:26 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Thanks for letting us know that you succeded.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
