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


Configuring the publication of event messages

You can configure the publication of event messages by using the mqsichangeproperties command to set properties for the pubsub component.

Before you begin

Read the following topics:

About this task

You can use the mqsichangeproperties command to control which integration node event messages are published by IBM® Integration Bus, and to ensure that they are delivered to the appropriate pub/sub broker. You can also choose which of the supported transports is used for publishing the event messages. For example, you can specify they are published through an MQ pub/sub broker, the built-in MQTT pub/sub broker, an external MQTT server, or a combination of MQ and MQTT brokers. By default, all event messages except for business 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 event messages) are published to the MQ pub/sub broker.

You can also control the types of event messages that are published to each type of broker; for example, you might choose to publish business event messages to an MQ pub/sub broker and all other event messages to the built-in MQTT pub/sub broker. Alternatively, you might choose to publish only operational event messages to one or more pub/sub brokers, and turn off the publication of all other event messages. For more information about the types of event in each group, see Event reports: general architecture.

Additionally, you can specify credentials to be used when you are publishing event messages to a secured MQTT server or a secured MQ pub/sub broker, by using the mqsisetdbparms command.

Follow these steps to configure the publication of event messages:

Procedure

  1. Use the enabled property of the mqsichangeproperties command to enable or disable the publication of event messages by the specified pub/sub broker. All integration node events are configured by event group (operational, admin, or business), and you can enable or disable the publication of event messages based on their type. For example, enter the following command to enable the publication of event messages to an MQTT broker for the publication of business event messages:
    mqsichangeproperties IBNODE -b pubsub -o BusinessEvents/MQTT -n enabled -v true
    By default, all integration node event messages except for business events are emitted to the built-in MQTT broker. If you want to publish business event messages, you must complete one of the following additional steps:
    • Enable publication for business events over the MQTT broker by setting the enabled property for the BusinessEvents/MQTT object to true.
    • Ensure that WebSphere MQ is installed and a queue manager is specified on the integration node so that business event messages can be published to the MQ pub/sub broker.
    By default, all integration node event messages are published to the MQ pub/sub broker provided that WebSphere MQ is installed and a queue manager is specified on the integration node.
  2. If you want to use an external MQTT server for the publication of event messages, or if you want to use a specific WebSphere MQ queue manager, use the policyURL property of the mqsichangeproperties command to specify the location of the policy that contains the connection details. For example:
    mqsichangeproperties IBNODE -b pubsub -o BusinessEvents/MQTT -n policyURL -v /apiv1/policy/MQTTPublish/example_mqtt_policy
    If the required policy has not been created, see Creating policies by using the command line for information about how to create it.
  3. Optional: If the MQTT server or MQ pub/sub broker that you configured in the previous step requires security credentials for connections, use the mqsisetdbparms command to specify these credentials. If you specify a ResourceName of mqtt::pubsubDefault or mq::pubsubDefault, the credentials that you specify are used by the integration node when publishing its event messages, unless a specific security identity is specified in the configured policy.
    For example, use the following command to specify that the user name myUserID and password myPassword are used when connecting to an external MQTT server for the publication of event messages:
    mqsisetdbparms IBNODE -n mqtt::pubsubDefault -u myUserID -p myPassword
  4. Ensure that the subscription has been configured correctly, so that the required event messages are received correctly following the configuration of the publication details. For example, if subscription was previously turned off in the web user interface, you must turn it on before published event messages can be received and processed for functions such as message flow statistics.

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