Learn more about Boomi's MQTT Connector


The SDK based MQTT connector is built to meet the evolving needs of IOT based real time integrations. This connector offers complete functional parity with its predecessor while addressing certain limitations observed in the earlier version. Additionally, it is designed to accommodate enhancements to support higher versions of the MQTT protocol.  

MQTT (Deprecated) and MQTT SDK connector comparison

 
 

MQTT (Deprecated)

MQTT (New)

MQTT Protocol version supported

3.x

3.x (now). 5.x (Future)

Supported Operations

Listen, Send

Listen, Send

Runtimes 

Basic runtimes

Basic runtimes, runtime cluster

Dynamic Topics

Not supported

Supported

Clean Session during listener restarts

Confusing experience and behavior when using Clean Session and Client ID fields

Improved user experience - When the Clean Session option is checked, all subscriptions are removed at session end. When unchecked, the specified Client ID is used for persistent sessions.

 

Dynamic Topics

SEND Operation:
The ‘Outbound Topic’ for the SEND operation can be dynamically set for each document at runtime using Document Property

Select Set Properties step > Properties to Set > Select Property Type ‘Document Property’ > Select Source Type ‘Connectors’ > Select Connector ‘MQTT’ > Select Property ‘Outbound Topic’.

 

 

LISTEN Operation

Users can also override the topic name and Quality of Service (QoS) properties for the LISTEN operation through Environment Extensions

On the process canvas, select ‘Extensions’ > Operation Settings


 

Clean Session Setting

When establishing a connection with an MQTT broker, the MQTT Connector allows users to specify whether the client session should be treated as clean or persistent. 

Clean Session Enabled: If Clean Session is checked, the client's session is considered "clean." The broker does not retain session state or queued messages between connections. Upon disconnect, all session-related subscriptions and acknowledgments are discarded.
 

 

Clean Session Disabled: If Clean Session is Unchecked, it implies persistent session state maintenance. The broker retains client subscriptions and undelivered messages, ensuring seamless message delivery and consumption upon reconnection. A Client ID is required for this feature.

 

 

By specifying this parameter, users can control how the session state is managed between the Boomi MQTT connector acting as a Client and the MQTT broker.

Runtimes

There is always only one active listener instance running across all basic runtime and runtime cluster nodes. It handles receiving messages from subscribed MQTT topics, ensuring consistency and avoiding conflicts while processing. In case of node failures, the Singleton implementation enables the Listen operation to run on remaining active nodes, providing better fault tolerance.