Configuring the built-in MQTT pub/sub broker
Configure the built-in MQTT pub/sub broker by using the mqsichangeproperties command, or by updating the configuration file in the work_path\components\integrationNodeName\config directory.
Before you begin
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 IP address that the MQTT broker process starts by updating the value of bind_address
in the configuration file in the work_path\components\integrationNodeName\config directory. By default, the MQTT broker process starts on the same host as the integration node; the default content of the file is bind_address localhost
.
mqsireportproperties IBNODE -b pubsub -o MQTTServer -n port
Complete the following steps to change the MQTT pub/sub broker port:
Procedure
Results
max_queued_messages count
The
maximum number of QoS 1 or 2 messages to hold
in the queue above those messages that are currently in flight. The
default is 100. Set to 0 for no
maximum (this value is not recommended).The max queued messages count is set in the configuration file. The configuration file used by the bipMQTT can be found under the work_path\components\integrationNodeName\config directory which contains a file with the same name as Integration Node name. For example:
bind_address localhost
Use the
following steps to alter the built-in configuration:- Stop the Node
- Append the following line to the file max_queued_messages <count> - where count is the number of inflight messages to be held
- Restart the Node for the built-in mqtt broker to pick up the changes
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.