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.
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 the publication of OperationalEvents and BusinessEvents, and the integration node built-in MQTT broker, either by using the mqsichangeproperties command or by editing the node.conf.yaml or server.conf.yaml configuration file. You can configure specific MQ or MQTT connection policies, for each of the OperationalEvents and BusinessEvents 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 server, you can create a policy that contains the connection details that you want to use. For information about creating policies, see Creating policies with the IBM App Connect Enterprise Toolkit.
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.
For details of all the event messages that can be published, see Subscribing to event message topics.
Follow these steps to configure the publication of event messages by using the mqsichangeproperties command:
Follow these steps to configure the publication of event messages by setting properties in the server.conf.yaml or node.conf.yaml configuration file: