IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


Event reports: operational information

Changes to the processing state of an integration node or an individual message flow publish events with predefined system topics.

The following system topics are used:
  • For publications on an MQ pub/sub broker:
    $SYS/Broker/integrationNodeName/Status
     
    $SYS/Broker/integrationNodeName/Status/ExecutionGroup/exec_grp_name
  • For publications on an MQTT pub/sub broker:
    IBM/IntegrationBus/integrationNodeName/Status
     
    IBM/IntegrationBus/integrationNodeName/Status/ExecutionGroup/exec_grp_name
where:
integrationNodeName
is the name of the integration node whose execution state has changed
exec_grp_name
is the name of the integration server that contains the message flow whose execution state has changed

The body of each publication is an XML message that gives additional information concerning the state change that caused the event to be triggered, specifically indicating whether the entity has been started or stopped.

For example, starting a message flow generates the following message:
<Broker uuid="1234" label="INODE1" version="1">
<ExecutionGroup uuid="5678">
  <Start>
   <MessageFlow uuid="7812"/>
  </Start>
 </ExecutionGroup>
</Broker>
Stopping an integration node generates the following message body:
<Broker uuid="1234" label="INODE1" version="1">
 <StatusChange state="Stopped"/>
</Broker>

Currently, the only states that are notified for both integration nodes and message flows are Started and Stopped.

These events are nonpersistent, retained publications.


au19710_.htm | Last updated 2015-03-27 19:27:33