As per Kimbert's suggestion, I have been 'experimenting' with them.
I quickly realised that to get anything out of the broker with the -x -p options on mqsiflowmonitoring command, you have to specifically configure monitoring events on a flow and deploy it. I used the sample HTTP & SOAP flows to gather this data.
Ok. that is not too bad. Luckily in our setup all the SOAP Inputs are done by a generic SubFlow. This means that one profile for all those nodes is possible.
The downside is that the output XML can't be used as a generic monitoring profile as the events take the names of the nodes in the flow rather than the node type.
So all of our HTTP & MQ based flows will have to have specific profiles.
If this is done by Configurable Service then that is only another 30 or so on top of the current 80+, mostly SAP services already being used.
I guess I will be writitng a script to parse the .msgflow files to get the input node names and create a flow specific profile automatically.
Oh, and 6.1.0.3 on Solaris, the mqsireportflowmonitoring ... -x -p command crashes if there is no profile loaded.[/url] _________________ 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.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum