MQTT Connector FAQ
MQTT Connector frequently asked questions (FAQ) are:
The Enable file persistence feature is available only on the on-premises installation and uses a file for persistent messages. Note that an object store enables persistent storage for CloudHub applications. Refer to the object store documentation for details.
Yes, MQTT Connector is supported on CloudHub and on cluster environments.
MQTT Connector is cluster-aware. MQTT brokers usually implement a client takeover mechanism that closes an old connection if a new connection request with the same client ID as the existing (old) connection is received and then accepts the new connection. The client takeover mechanism can become a problem if you want to deploy an application in a cluster, and still provide an explicit client ID that identifies the client. MQTT Connector provides client ID generators that help you set a static client ID, set a client ID with a dynamic component to adjust to different deployment scenarios, or define your custom client ID generator.
For further information, refer to the set a Client ID with MQTT Connector documentation.
MQTT Connector authentication supports user and password, and certificate-based authentication (TLS or WSS). Refer to the configure credentials for authentication documentation.
Refer to the troubleshoot MQTT Connector documentation to learn how to enable verbose logging in DEBUG mode for the connector, for Eclipse Paho driver and the Mosquitto broker.
MQTT Connector works with any MQTT version 3.x compliant server also known as MQTT broker. To configure the server, refer to your MQTT broker’s documentation, for example, the Eclipse Mosquitto broker documentation.
MQTT Connector uses Eclipse Mosquitto libraries. The ArtifactID is
To get release notes for Eclipse Mosquitto library, refer to the Eclipse public repository.
Are there any permission, roles, or additional configuration required on the broker side to connect with our credentials using MQTT Connector?
No, there aren’t any additional permissions or configuration requirements to connect to MQTT version 3.x compliant MQTT brokers. On the MQTT broker side, you do need to configure the listeners properly.