Event message architecture
Integration nodes publish messages on reserved topics after significant events within the integration node. By subscribing to these topics, a client is informed when these events occur.
For each topic, the type of event and message body are explained. The body of these messages is either in JSON or XML format, depending on the topic.
An event publication can contain more than one entry if the topic is the same (for example, if several message flows are created in the same operation).
$SYS/Broker/integrationNodeName/event_type/...
For
events that are published that use MQTT as the transport, the
notation is as follows:IBM/IntegrationBus/integrationNodeName/event_type/...
This specification of topics helps client applications to filter events, which are based on the integration node from which the event originated and the type of event. The client applications register subscriptions for these topics to receive the reports.
For
specific events, additional information is included in the topic to
help filter on the specific object that raised the event. The
inclusion of the string Broker
(or for MQTT, IntegrationBus
)
at the second level of the topic hierarchy allows for future extension
to additional subsystems that publish system management events
through the integration node.