| Author |
Message
|
| goffinf |
 Posted: Wed Aug 24, 2011 7:47 am Post subject: monitoring events topic |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Version: 6.1.0.3
The infocentre states that the topic used for broker monitoring events is :-
$SYS/Broker/<brokerName>/Monitoring/<executionGroupName>/<flowName>
Is it possible to use different topic names ?
We use monitoring events for a 3 different purposes each of which has a specific consumer flow which works with the different content that is sent.
We would like to be able to subscribe to each topic name so only event messages of the expected type are passed to the subscriber app.
Not sure i explained that very well, but basically can we configure the in-built monitoring events to publish to more than one topic name.
Regards
Fraser. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Aug 24, 2011 7:52 am Post subject: Re: monitoring events topic |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| goffinf wrote: |
| basically can we configure the in-built monitoring events to publish to more than one topic name. |
AFAIK no, but you have all the tricks, tips, wheezes and dodges you'd use with any pub/sub. Content based filtering for instance.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| goffinf |
| Posted: Thu Aug 25, 2011 2:46 am Post subject: Re: monitoring events topic |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| Vitor wrote: |
| AFAIK no, but you have all the tricks, tips, wheezes and dodges you'd use with any pub/sub. Content based filtering for instance. |
Good idea. Problem is that broker event messages include namespaces and filters don't appear to work in that case.
That said the InfoCentre suggests that it *should* be possible
| InfoCentre wrote: |
| You cannot use the XMLNS parser, or the MRM XML parser with namespace, for content-based filtering, but you can use the XML parser, and reference an element that is in the format namespace:field because the XML parser treats this reference as one element called namespace:field. |
But my attempts to register a subscription (via RFHUtils) with a topic string in that format don't work (it could be an RFHUtil issue I suppose ?).
So here's what I've tried ..
in the Filter entry field I put :-
Body.wmb:event.wmb:eventPointData.wmb:eventData.(XML.Attribute)wmb:eventSourceAddress LIKE 'MF_%'
But the subscription was NOT created. In another thread someone suggested this was because of the presence of the colons ( .
Tried adding double-quotes around it all, and the subscription WAS created but no messages were received in the subscription queue (I am certain that the eventSourceAddress value is MF_xxxxxxx - see below). So I don't think that filter format is correct.
Tried replacing the prefixes wmb with the actual namespace (suggestion by jeff lowrey in another thread). No subscription created.
stumped ??
Fraser.
This is what a monitoring event looks like :-
| Code: |
<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="6103" wmb:eventSchemaVersion="6.1.0.3" wmb:eventSourceAddress="MF_HTTPInput.transaction.Start">
<wmb:eventIdentity wmb:eventName="MF_HTTPInput.TransactionStart"/>
<wmb:eventSequence wmb:creationTime="2011-08-09T12:18:09.973"/>
<wmb:eventCorrelation wmb:localTransactionId="8fb17e0d-23d8-4a8f-a353-cdb0628a0093" wmb:parentTransactionId="dc5a8063-0d3a-4cd5-8e4d-92beb9b86d94" wmb:globalTransactionId="a901eed9-4dff-4ac2-9e4f-565936b1c1c8"/>
</wmb:eventData>
<wmb:messageFlowData>
<wmb:broker wmb:name="WBRK61_DEFAULT_BROKER" wmb:UUID="56ff65a6-1d01-0000-0080-cc3cc2f31967"/>
<wmb:executionGroup wmb:name="test" wmb:UUID="f1d2fdb6-3001-0000-0080-f3ca4db64844"/>
<wmb:messageFlow wmb:uniqueFlowName="WBRK61_DEFAULT_BROKER.test.myflow" wmb:name="myflow" wmb:UUID="36bc1faa-3101-0000-0080-c030a64febb4" wmb:threadId="4080"/>
<wmb:node wmb:nodeLabel="MF_HTTPInput" wmb:nodeType="ComIbmWSInputNode"/>
</wmb:messageFlowData>
</wmb:eventPointData>
</wmb:event>
|
[/code] |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 25, 2011 2:53 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
There is an XSD for the message you know! That might help you in doing the filtering.
_________________
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 |
|
|
| goffinf |
| Posted: Thu Aug 25, 2011 2:56 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| smdavies99 wrote: |
| There is an XSD for the message you know! That might help you in doing the filtering. |
Yes I have the XSD.
Its not that the XPath is incorrect, its that it appears the filter can't include the colon characters, or at least thats what appears to be the case.
Do you believe otherwise ?
Fraser. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 25, 2011 4:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Perhaps this article might help http://msdn.microsoft.com/en-us/library/ms950779.aspx
_________________
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 |
|
|
| goffinf |
| Posted: Thu Aug 25, 2011 4:34 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
I'm not sure what it is you are trying to tell me. If you think there is something specifcally wrong with what I'm doing please say so. I'm not asking for a code solution, I'm more than happy to sort that out for myself.
I have been using XML+Namespace, XPAth1 and 2 XSLT1 and 2 for many years so I *think* I'm pretty competent here ??
According to InfoCentre and as I'm sure you are aware, these filters are NOT XML namespace aware (i.e. they don't support prefix bindings), but it *is* suggested that they will treat prefix:local-name as a literal name ?
The area that I am certainly weak in is specifiying filters for subscriptions. So for example, I'm, not sure that using (XML.Attribute) is correct (given that XMLNSC is not supported) ?
Fraser. |
|
| Back to top |
|
|
|
|
