| Author |
Message
|
| smdavies99 |
 Posted: Tue Sep 07, 2010 4:53 am Post subject: Broker Flow Monitoring Output |
 |
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If I just enable the flowmonitoring via the meqsichangeflowmonitoring command and then subscribe to its publicvation, as expected, Broker does publish the Start & End events.
However if the eventStart is from a flow where the first node in an MQInput Node, the data emitted is different from say a SOAP Input Node.
For the MQInput Node, there is extra data. Specifically,
| Code: |
<wmb:bitstreamData>
<wmb:bitstream wmb:encoding="base64Binary">TUQgnM6T... VSZXBvcnQ+</wmb:bitstream>
</wmb:bitstreamData>
</wmb:event>
|
right at the end of the message.
Is there anyway without using event profiles to make all the eventStart Nodes have this extra payload data?
_________________
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 |
|
 |
| kimbert |
| Posted: Tue Sep 07, 2010 5:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
However if the eventStart is from a flow where the first node in an MQInput Node, the data emitted is different from say a SOAP Input Node.
For the MQInput Node, there is extra data |
Yes - the presence/absence of the bitstreamData tag depends on the type of input node. Nodes which can efficiently produce the tag do so automatically, others do not.
| Quote: |
| Is there anyway without using event profiles to make all the eventStart Nodes have this extra payload data? |
I'm afraid not.
I could argue that it's good practice to create an event profile anyway, rather than relying on default behavior. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 07, 2010 6:04 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| kimbert wrote: |
Yes - the presence/absence of the bitstreamData tag depends on the type of input node. Nodes which can efficiently produce the tag do so automatically, others do not.
|
Thanks. I feared as much. If I have time I'll investigate using a monitoring profile.
However, is there a list somewhere that identifies the nodes that do and don't include the payload information.
_________________
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 |
|
|
| kimbert |
| Posted: Tue Sep 07, 2010 6:13 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| There is no published list. IBM is implicitly guiding users not to rely on the default behaviour. As far as I remember, the MQInput node supplies the bitstream, the SAP nodes do not, and the File node does not. Nodes which support streaming do not include the bitstream because it could, potentially, be huge. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 07, 2010 6:21 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Thanks Kimbert.
I sort of expected that answer.
I'm only interested in MQ, SOAP & HTTP nodes.
sigh.
It looks like it will have to be a monitoring profile after all.
_________________
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 |
|
|
| kimbert |
| Posted: Tue Sep 07, 2010 7:13 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
sigh.
It looks like it will have to be a monitoring profile after all.
|
For my own interest, why the sigh? Is it the difficulty of creating it, or the hassle of deploying it? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 07, 2010 7:29 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Sorry, that was a big sigh.
Yes, the main reason is the hassle of deploying.
Ok, I haven't created one before but I'll start with the example in the docs. It is just finding the time to do all the 'extra' stuff needed to make this all work nicely as well as all the myriad of other things that seem to head my way on a daily basis.
I'll live with the no profile version for the time being. This will alow us to shake down the main flow. The payload stuff would have been the icing on the cake. We could write it away in the monitoring flow rather than in the flows themselves.
_________________
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 |
|
|
| kimbert |
| Posted: Tue Sep 07, 2010 9:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Ok, I haven't created one before but I'll start with the example in the docs. |
There's an easier way than that. You can set up your monitoring properties using the node properties, deploy the flow, and then get the equivalent monitoring profile created for you. See http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ac60384_.htm
| Quote: |
Export a message flow's monitoring profile
Use the following command to export a profile to file myMonProf.xml
Issue the following command on Linux, Unix, or Windows:
mqsireportflowmonitoring BROKER1 -e default -f PurchaseOrder -x -p myMonProf.xml
Issue the following command on z/OS:
z/OS platform
F MI10BRK,rm e='default',f='PurchaseOrder',x='yes',p='myMonProf.xml'
If monitoring for a message flow is configured using monitoring properties, rather than a monitoring profile configurable service, the command creates and returns the equivalent monitoring profile XML file. |
|
|
| Back to top |
|
|
|
|
