WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
WebSphere Message Broker event reports: operational information
Changes to the processing state of a broker or an individual message flow publish events with predefined system topics.
The following system topics are used:
$SYS/Broker/broker_name/Status
$SYS/Broker/broker_name/Status/ExecutionGroup/exec_grp_name
where:
- broker_name
- is the name of the broker whose execution state has changed
- exec_grp_name
- is the name of the execution group 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="Broker1" version="1">
<ExecutionGroup uuid="5678">
<Start>
<MessageFlow uuid="7812"/>
</Start>
</ExecutionGroup>
</Broker>
Stopping a broker generates the following message body:
<Broker uuid="1234" label="Broker1" version="1">
<StatusChange state="Stopped"/>
</Broker>
Currently, the only states that are notified for both brokers and message flows are Started and Stopped.
These events are nonpersistent, retained publications.