| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IIB/WMBIMB event structure versus Common Based Events (CBE) |
« View previous topic :: View next topic » |
| Author |
Message
|
| aspre1b |
 Posted: Mon Apr 17, 2017 11:49 pm Post subject: IIB/WMBIMB event structure versus Common Based Events (CBE) |
 |
|
Voyager
Joined: 05 Jul 2007
Posts: 78
Location: Coventry, UK
|
Hi all,
I'm looking at putting in a standard event structure across many integration components. According to the RedBook "Connecting Your Business Using IBM WebSphere Message Broker V7 as an ESB", the event emitted from WBIMB is compatible with the CBE:
"Message Broker is configured to emit events. The event is emitted in an XML format that is compatible with the Common Based Event (CBE) specification and allows integration with other monitoring applications."
https://books.google.co.uk/books?id=QRLCAgAAQBAJ&pg=PA430&lpg=PA430&dq=why+doesn+message+broker+use+common+based+event&source=bl&ots=oLJrQjbCuv&sig=Xmzs4tE0K3xavJ6upR68t2LCSkg&hl=en&sa=X&ved=0ahUKEwipzIuOuq3TAhXHAsAKHWb_C1gQ6AEIQjAE#v=onepage&q=why%20doesn%20message%20broker%20use%20common%20based%20event&f=false
I'm a little confused by use of the word compatible, as the CBE standard has a root element of "CommonBaseEvent", and there are two mandatory complex types, "sourceComponentId" and "situationInformation". They are not present in the wbimb event, but the fields look to be similar.
It would appear compatible means there are fields that map onto the CBE structure, but wbimb uses an altogether different structure.
Have I got the wrong end of the stick here?
Is there a plan to align IIB events with the CBE structure in the future?
WBIMB event:
| Code: |
<wmb:event xmlns:wmb="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0/monitoring/event">
<wmb:eventPointData>
<wmb:eventData wmb:productVersion="10005" wmb:eventSchemaVersion="6.1.0.3" wmb:eventSourceAddress="MQ Input.terminal.out">
<wmb:eventIdentity wmb:eventName="MQ Input.OutTerminal"/>
<wmb:eventSequence wmb:creationTime="2017-04-10T09:00:11.520431Z" wmb:counter="1"/>
<wmb:eventCorrelation wmb:localTransactionId="414d5120746573742020202020202020ab04e55820035a1a" wmb:parentTransactionId="" wmb:globalTransactionId="414d5120746573742020202020202020ab04e55820035a1a"/>
</wmb:eventData>
<wmb:messageFlowData>
<wmb:broker wmb:name="test" wmb:UUID="adf665be-598e-4c02-b1b8-e82519c9d018"/>
<wmb:executionGroup wmb:name="default" wmb:UUID="6b049434-168e-4bf5-b459-dc77802d0324"/>
<wmb:messageFlow wmb:uniqueFlowName="test.default.test_APP.com.cbs.test" wmb:name="com.cbs.test" wmb:UUID="b49c50de-b492-4b85-91ae-ab6f2095849d" wmb:threadId="42348"/>
<wmb:node wmb:nodeLabel="MQ Input" wmb:nodeType="ComIbmMQInputNode" wmb:terminal="out"/>
</wmb:messageFlowData>
</wmb:eventPointData>
<wmb:applicationData xmlns="">
<wmb:simpleContent wmb:name="CodedCharSetId" wmb:value="1208" wmb:dataType="integer"/>
<wmb:simpleContent wmb:name="RoutingInfo_ServiceName" wmb:value="AffordabilityCalculation" wmb:dataType="string"/>
</wmb:applicationData>
<wmb:bitstreamData>
<wmb:bitstream wmb:encoding="base64Binary"></wmb:bitstream>
</wmb:bitstreamData>
</wmb:event>
<?xml version="1.0" encoding="UTF-8"?>
<cbe:CommonBaseEvent xmlns:cbe="http://www.ibm.com/AC/commonbaseevent1_1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ibm.com/AC/commonbaseevent1_1 CBE%20schema%20v1.1.xsd">
<sourceComponentId component="FILENET#5.2.1" subComponent="CPE" componentIdType="NAME" location="myhost" locationType="FQHostname" />
<situationInformation globalInstanceId="A1E0C298CA1312A0C503F6EC01B94D3B" localInstanceId="9.27.11.27.xx.2016100902534.002000-240" creationTime="2017-02-21T09:30:47.123456Z" severity="10" priority="50">
<situationType category="STORED" successDisposition="SUCCESSFUL" situationQualifier="BLANK" reasoningScope="Application" connectDisposition="Internal"/>
</situationInformation>
</cbe:CommonBaseEvent> |
|
|
| Back to top |
|
 |
| timber |
| Posted: Sun Apr 23, 2017 12:05 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Quote: |
I'm a little confused by use of the word compatible, as the CBE standard has a root element of "CommonBaseEvent", and there are two mandatory complex types, "sourceComponentId" and "situationInformation". They are not present in the wbimb event, but the fields look to be similar.
It would appear compatible means there are fields that map onto the CBE structure, but wbimb uses an altogether different structure. |
It means that the IIB monitoring events are not CBE events but they do have all of the data required to construct a CBE event. |
|
| Back to top |
|
|
| aspre1b |
| Posted: Wed Apr 26, 2017 5:56 am Post subject: |
|
|
Voyager
Joined: 05 Jul 2007
Posts: 78
Location: Coventry, UK
|
Thanks Timber.
Its a shame that there isn't an alignment with CBE or the ability to tick a box to generate a CBE instead of the standard format.
Of course we could programmatically construct the CBE and publish using a publish node, but that would feel like re-inventing the wheel as we would like to have a single standard. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
