Configuring the publication of event messages
You can configure the publication of event messages, including whether messages are published for an event message group, and the pub/sub broker to which the messages are published.
Before you begin
About this task
- The built-in MQTT pub/sub broker
- An MQTT pub/sub broker on an external MQTT server
- An MQ pub/sub broker
- A combination of MQ and MQTT pub/sub brokers
- WebSphere® MQ is not installed, or WebSphere MQ is installed but a queue manager is not specified on the integration node
- By default, the messages are published to the following locations:
- OperationalEvents messages are published to the built-in MQTT pub/sub broker.
- AdminEvents messages are published to the built-in MQTT pub/sub broker.
- BusinessEvents messages are not published.
- WebSphere MQ is installed and a queue manager is specified on the integration node
- By default, the messages are published to the following locations:
- OperationalEvents messages are published to the MQ pub/sub broker and the built-in MQTT pub/sub broker.
- AdminEvents messages are published to the MQ pub/sub broker and the built-in MQTT pub/sub broker.
- BusinessEvents messages are published to the MQ pub/sub broker.
In either deployment configuration, if you want to publish BusinessEvents messages to the built-in MQTT pub/sub broker, you must explicitly enable the publication of the BusinessEvents group to the built-in MQTT pub/sub 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 message groups.
If you want to use an external MQTT server instead of the built-in MQTT broker, or you are using the MQ pub/sub broker and you want to use a different queue manager to the queue manager that is specified on the integration node, you can use the mqsichangeproperties command to specify a policy that contains the connection details that you want to use. For information about creating policies, see Creating policies by using the command line.
To use a secured MQ pub/sub broker or an MQTT server that requires a user name and password, use the mqsisetdbparms command to define the credentials to use for the connection. If a specific identity is not defined in the configured policy, the integration node uses the security identity pubsubDefault when publishing event messages. 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.
mqsireportproperties IBNODE -b pubsub -o AdminEvents/MQTT -n enabled
For details of all the event messages that can be published, see Subscribing to event message topics.
You can configure whether events are published, and where they are published to, by using the mqsichangeproperties command or operational policy.
Follow these steps to configure the publication of event messages: