Author |
Message
|
skadaval |
Posted: Wed Nov 18, 2009 11:28 am Post subject: unable to add payload in wmb monitoring events |
|
|
Novice
Joined: 26 Mar 2008 Posts: 15
|
I was unable to extract Key fields from the message payload. If I give $Body in event payload tab it shows me entire message in wmb generated event at Location: :applicationData/wmb:complexContent. Even I tried with sample example provided IBM(WMBMonitorEvents project) but no luck.
To extract empId from message, I given xpath expression: $Body/tns:events/s1:empId in Event Payload under Data location.
Event message for transaction start:
<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="6105" wmb:eventSchemaVersion="6.1.0.3" wmb:eventSourceAddress="SAMPLE.IN.transaction.Start">
<wmb:eventIdentity wmb:eventName="SAMPLE.IN.TransactionStart"/>
<wmb:eventSequence wmb:creationTime="2009-11-06T21:00:08.591"/>
<wmb:eventCorrelation wmb:localTransactionId="5d6bbee0-4101-45c0-9c0a-ec26eb940257" wmb:parentTransactionId="ced5bb3f-15a6-4250-b698-518b2da22eec" wmb:globalTransactionId="1826e24d-f720-4407-b01a-54e2fd2f9270"/>
</wmb:eventData>
<wmb:messageFlowData>
<wmb:broker wmb:name="WBRK61_DEFAULT_BROKER" wmb:UUID="40d29158-2401-0000-0080-e9ffb95fcc8b"/>
<wmb:executionGroup wmb:name="default" wmb:UUID="ddd79158-2401-0000-0080-e9ffb95fcc8b"/>
<wmb:messageFlow wmb:uniqueFlowName="WBRK61_DEFAULT_BROKER.default.Sample_Events" wmb:name="Sample_Events" wmb:UUID="4c2b66b6-2401-0000-0080-89198fe0ad7c" wmb:threadId="4108"/>
<wmb:node wmb:nodeLabel="SAMPLE.IN" wmb:nodeType="ComIbmMQInputNode" wmb:detail="SAMPLE.IN"/>
</wmb:messageFlowData>
</wmb:eventPointData>
<wmb:bitstreamData>
<wmb:bitstream wmb:encoding="base64Binary">TUQgIAIAAAAAAAAACAAAAP////8AAAAAIgIAALUBAAAgICAgICAgIAAAAAAAAAAAQU1RIFdCUks2MV9ERUZBVTyD9EogABUDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFdCUks2MV9ERUZBVUxUX1FVRVVFX01BTkFHRVIgICAgICAgICAgICAgICAgICAgIHNrYWRhdmFsYSAgIBYBBRUAAACbC8EeD/+PzwvaWRlbnRpZmllcj4NCiAgICAgICAgICAgICAgICAgICAgIDwhLS1PcHRpb25hbDotLT4NCiAgICAgICAgICAgICAgICAgICAgIDxkZXNjcmlwdGlvbj4/PC9kZXNjcmlwdGlvbj4NCiAgICAgICAgICAgICAgICAgIDwvZG9lOm9yZ2FuaXphdGlvbmFsRnVuY3Rpb24+DQogICAgICAgICAgICAgICAgICA8IS0tT3B0aW9uYWw6LS0+DQogICAgICAgICAgICAgICAgICA8ZG9lOm9yZ2FuaXphdGlvbmFsVGl0bGU+DQogICAgICAgICAgICAgICAgICAgICA8IS0tT3B0aW9uYWw6LS0+DQogICAgICAgICAgICAgICAgICAgICA8aWRlbnRpZmllcj4/PC9pZGVudGlmaWVyPg0KICAgICAgICAgICAgICAgICAgICAgPCEtLU9wdGlvbmFsOi0tPg0KICAgICAgICAgICAgICAgICAgICAgPGRlc2NyaXB0aW9uPj88L2Rlc2NyaXB0aW9uPg0KICAgICAgICAgICAgICAgICAgPC9kb2U6b3JnYW5pemF0aW9uYWxUaXRsZT4NCiAgICAgICAgICAgICAgIDwvZG9lOmFzc2lnbm1lbnRzPg0KICAgICAgICAgICAgPC9kb2U6c3RhZmY+DQogICAgICAgICAgICA8IS0tT3B0aW9uYWw6LS0+DQogICAgICAgICAgICA8ZG9lOmV2ZW50VHlwZT4/PC9kb2U6ZXZlbnRUeXBlPg0KICAgICAgICAgPC90ZW06dXBkYXRlRXZlbnQ+DQogICAgICA8L3RlbTpldmVudHM+DQogICA8L3NvYXBlbnY6Qm9keT4NCjwvc29hcGVudjpFbnZlbG9wZT4=</wmb:bitstream>
</wmb:bitstreamData>
</wmb:event>
Any help would be appreciated |
|
Back to top |
|
 |
kimbert |
Posted: Wed Nov 18, 2009 2:24 pm Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Quote: |
If I give $Body in event payload tab it shows me entire message in wmb generated event at Location: :applicationData/wmb:complexContent |
That is the correct behaviour, right? You asked for the entire message body, and that is what you got.
Quote: |
To extract empId from message, I given xpath expression: $Body/tns:events/s1:empId in Event Payload under Data location.
|
I don't know what your message tree looks like, so I cannot say whether that XPath is correct.
Long shot: When you constructed the Xpath, did you provide namespace prefix definitions for 'tns' and 's1'? |
|
Back to top |
|
 |
skadaval |
Posted: Thu Nov 19, 2009 6:15 am Post subject: |
|
|
Novice
Joined: 26 Mar 2008 Posts: 15
|
thanks for your prompt response.
your are right. issue is with namespace. my message contains soap enevelope and my xpath expression doesnt contain soap enevelop. After adding soap enevelop to the xpath expression I can able to extract key fields from message.
My bad thank you kimbert for the valuable information issue resolved. |
|
Back to top |
|
 |
AkankshA |
Posted: Thu Nov 19, 2009 7:21 pm Post subject: |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
skadaval wrote: |
thanks for your prompt response.
your are right. issue is with namespace. my message contains soap enevelope and my xpath expression doesnt contain soap enevelop. After adding soap enevelop to the xpath expression I can able to extract key fields from message.
My [b]bad [/b]thank you kimbert for the valuable information issue resolved. |
Just one typo error can sometimes change the whole world around :O _________________ Cheers |
|
Back to top |
|
 |
smdavies99 |
Posted: Fri Nov 20, 2009 12:02 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Quote: |
Just one typo error can sometimes change the whole world around :O |
Or make you eat SOAP  _________________ 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 |
|
 |
|