| Author |
Message
|
| WMBSAM |
 Posted: Fri Sep 20, 2013 8:00 am Post subject: auditing issue with collector node |
 |
|
Voyager
Joined: 02 Oct 2009
Posts: 90
Location: Atlanta
|
Trying to configure auditing events in messageflow with collector node in it.
designed a flow as : MQinputNode --> collectorNode-->computenode-->FileOutputNode
the main issue lies in correlating the individual child messages(at MQinoutnode)with unique transactionID with the parenttransactionID assigned to the MergedFile that gets generated after the collector node . any suggestions?
description: the collector node merges every 10 messages to 1 file . so before message reaches collector node . i have assigned globaltransaction ID for each message and after the file is generated once message passed through collector node it completely acts as a new transaction and then i loose all the globaltransaction i have assigned before and i am left with assigning only a unique transaction to the merged file and now i cannot correlate the individual msg transaction ids with the merged file transaction id. |
|
| Back to top |
|
 |
| Simbu |
| Posted: Fri Sep 20, 2013 8:22 am Post subject: Re: auditing issue with collector node |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| WMBSAM wrote: |
Trying to configure auditing events in messageflow with collector node in it.
designed a flow as : MQinputNode --> collectorNode-->computenode-->FileOutputNode
the main issue lies in correlating the individual child messages(at MQinoutnode)with unique transactionID with the parenttransactionID assigned to the MergedFile that gets generated after the collector node . any suggestions?
description: the collector node merges every 10 messages to 1 file . so before message reaches collector node . i have assigned globaltransaction ID for each message and after the file is generated once message passed through collector node it completely acts as a new transaction and then i loose all the globaltransaction i have assigned before and i am left with assigning only a unique transaction to the merged file and now i cannot correlate the individual msg transaction ids with the merged file transaction id. |
If I'm correct, A transaction break occurs at the Collector node and that means the single flow will act as two different flow. Need to find a way to correlate the event message. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Sep 20, 2013 8:23 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
You have to think of a flow with a collector node in it as two separate entities.
The first is to the left of the collector node. This is where you deposit the items into the collection.
The second is to the right of the node. This is the thread that contains the collection.
Why don't you go back and examine the flow again with this information in mind.
_________________
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 |
|
|
| WMBSAM |
| Posted: Fri Sep 20, 2013 8:35 am Post subject: |
|
|
Voyager
Joined: 02 Oct 2009
Posts: 90
Location: Atlanta
|
| @ Simbu Yes you are correct...i am not sure even after accepting as 2 different flows not sure how to correlate them. |
|
| Back to top |
|
|
| Simbu |
| Posted: Fri Sep 20, 2013 9:08 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
You have to use monitoring profile to do this. Choose a parent correlator which is accessible by both MQInput and Collector Node. Configure monitoring profile accordingly.
| Quote: |
You cannot use monitoring properties to configure transaction events on the following nodes:
Collector node
Resequence node
Use a monitoring profile instead; see Configuring monitoring event sources using a monitoring profile. |
|
|
| Back to top |
|
|
| WMBSAM |
| Posted: Fri Sep 20, 2013 11:34 am Post subject: |
|
|
Voyager
Joined: 02 Oct 2009
Posts: 90
Location: Atlanta
|
Ahh thats a good info. let me try that and fix it.
thanks for the quick response again.  |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Sep 21, 2013 7:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
If for some reason you need to correlate individual messages to their collector total post flow, I would suggest that you do that where you allocate the global id for the collector node and store that information in a DB.
This way you can always cross check using the DB
You will have 10 values from before the collector node and 1 value from after the collector node. If you then correlate those to the global ID you will have a full audit trail....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
