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


Publishing event messages

All integration node event messages can be published through the built-in MQTT broker, an external MQTT server, an MQ pub/sub broker, or a combination of MQ and MQTT pub/sub brokers.

The following IBM® Integration Bus functions use a pub/sub broker to publish and subscribe to event messages: If you want to receive event messages for any of these events (which includes viewing statistics in the web user interface), you must ensure that event publication is enabled and that a pub/sub broker has been configured. For information about completing these tasks, see Configuring the publication of event messages and Configuring the built-in MQTT broker.
IBM Integration Bus event messages are categorized in the following three groups:

The event types that are contained these groups are described in Event reports: general architecture.

You can configure whether events are published, and where they are published to, by using the mqsichangeproperties command or operational policy.

By default, all event messages except for monitoring events are published to the built-in MQTT broker. If WebSphere® MQ is installed and a queue manager is specified on the integration node, all event messages (including business events) are published to the MQ pub/sub broker. This means that, by default, message flow statistics, resource statistics, integration node status, integration server status, integration server configuration, and workload management emit events to the built-in MQTT broker. If you want to publish monitoring events, you must either ensure that WebSphere MQ is installed and a queue manager is specified on the integration node, or you must enable the publication of the BusinessEvents group over the built-in MQTT broker.

You can change the settings for event publication and the built-in MQTT broker by using the mqsichangeproperties command. You can use mqsichangeproperties to have a specific (local) policy for MQ or MQTT, which can be different for each of the three event groups. For more information, see Configuring the publication of event messages.

If you want to use an external MQTT server instead of the built-in MQTT broker, you can use the mqsichangeproperties command to specify a policy that contains the connection details of the MQTT server. Similarly, if you are using the MQ pub/sub broker and want to use a different queue manager to the queue manager that is specified on the integration node, use a policy for the connection details. For information about creating policies, see Creating policies by using the command line.

To use an MQTT server that requires a user name and password, or a secured MQ pub/sub broker, use the mqsisetdbparms command to define the credentials to use for the connection. The integration node uses the security identity pubsubDefault when publishing its event messages if a specific identity is not defined in the configured policy. If pubsubDefault has been associated with security credentials by using the mqsisetdbparms command, then these credentials are used; otherwise, no credentials are used. For more information, see mqsisetdbparms command.

You can also view the current event configuration by using the pubsub property of the mqsireportproperties command. For example, use the following command to show whether the publication of admin event messages is enabled on the MQTT broker:
mqsireportproperties IBNODE -b pubsub -o AdminEvents/MQTT -n enabled

MQ and MQTT use different topic roots for publication. For more information about how event types and event topics are represented, see Event reports: general architecture.


bq28100_.htm | Last updated 2015-03-27 19:28:34