| Author |
Message
|
| muralihegde |
 Posted: Mon Feb 03, 2014 6:41 am Post subject: Usage of Accounting Origin in Message Flow accounting static |
 |
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
| We are using WMB 8.0.0.3. I have been trying to see how the message flow statics can be used to identify the run time performance issues. I have been able to do the basic set up, use the XML and the default text format etc. Has anyone used the Accounting Origin effectively and what are the ways and scenarios this can be used? |
|
| Back to top |
|
 |
| McueMart |
| Posted: Mon Feb 03, 2014 7:35 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
Accounting Origin can be used to differentiate between different message 'origins' into the flow.
For example imagine you have Shop1, Shop2 and Shop3 sending messages in your message flow. Using Accounting Origin you will be able to view the data which has come from the 3 individual sources.
Note that it does require you to configure the input message to identify it's Accounting Origin (read the infocenter for how to do this).
Check out IS03 SupportPac for a better way of consuming the statistics data. |
|
| Back to top |
|
|
| muralihegde |
| Posted: Wed Feb 05, 2014 5:33 am Post subject: |
|
|
Centurion
Joined: 30 Apr 2002
Posts: 108
|
Thanks I have downloaded ISA03 and exploring that.
One more question.. how do we know the which step/node in WMB flow is slower ?
TotalElapsedTime, MaximumElapsedTime', MinimumElapsedTime' --> do they indicate the processing time that a node took? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 05, 2014 6:05 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| muralihegde wrote: |
Thanks I have downloaded ISA03 and exploring that.
One more question.. how do we know the which step/node in WMB flow is slower ?
TotalElapsedTime, MaximumElapsedTime', MinimumElapsedTime' --> do they indicate the processing time that a node took? |
Forget just plain processing time...
Imagine you have a flow with a call out to a web service via http or soap. If that service is slow, processing time may be very small but wait time at the httpRequest or SoapRequest node will be high.
Elapsed time in conjunction with wait time is a good KPI. But you need both to understand whether it is the flow or the resource you are calling...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| McueMart |
| Posted: Wed Feb 05, 2014 11:01 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
| Quote: |
| One more question.. how do we know the which step/node in WMB flow is slower ? |
Have a play with IS03 and you will be able to see for yourself (hopefully)! As fbj_saper mentioned, there is a big different between elapsed time and cpu time and the statistics can help you identify the parts of your flow which are either CPU intensive, or are slow due to other reasons. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 05, 2014 1:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And remember CPU intensive does not mean that you can't do anything about it. It just means that it may well be your fault and you should review your coding with best practices in mind! Wait intensive steps means that the resource your are accessing is the bottleneck. Talk to the people managing that resource to see if you can get some improvement, or switch your design from synchronous invocation to asynchronous invocation...
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
