About this task
The built-in MQTT broker is enabled by default, and it is the default transport for the
publication of operational and admin events by an integration node (unless WebSphere® MQ is installed and a queue manager is specified on the integration
node; see Configuring the publication of event messages).
You can modify the configuration of the built-in MQTT broker by using the
mqsichangeproperties command. Use the
enabled
property for the MQTTServer object in the pubsub component to enable or disable the built-in MQTT
broker, and the
port property to specify the port to be used by the broker. By
default, the
enabled property is set to
true and the port is set to
11883. When an
integration node starts, the built-in MQTT broker starts on the port configured by the
port property for the MQTTServer object in the pubsub component.
Note: If more
than one integration node is configured with the same MQTTServer port, only one MQTT broker will
start. All integration nodes that are using the same MQTTServer port, will use the same MQTT broker
to publish their events. Subscribers that connect to the MQTT broker receive all the events that are
published by the broker, unless the subscriber includes the name of the integration node in their
subscriptions.
You can view the current configuration of the built-in MQTT broker by using the
mqsireportproperties command. For example, use the following command
to view the port that is used by the built-in MQTT
broker:
mqsireportproperties IBNODE -b pubsub -o MQTTServer -n port
Complete the following steps to change the MQTT pub/sub broker port:
What to do next
By default, all event groups except the BusinessEvents group are enabled for MQTT transport. The BusinessEvents group is enabled by default for the MQ pub/sub
broker. The BusinessEvents group includes monitoring
events. If you want to publish monitoring events to the built-in MQTT broker, you must configure the
BusinessEvents group to enable MQTT publication by
using the mqsichangeproperties command. For an example, and
more information about how to specify a pub/sub broker for specific types of event, see Configuring the publication of event messages.