Change Header
Change Type: Preview
Product area: Platform services
Component: MQTT
Technical details
Build artifact: mqtt-service
Change Description
Preview
This feature is in Public Preview, that is, it is not enabled by default and may be subject to change in the future.
To determine whether the feature is available for your tenant, open the Administration application and navigate to Ecosystem > Microservices.
If you see the Mqtt-service microservice subscription for your tenant, the feature is already available.
Otherwise, please contact product support to request the microservice subscription for your tenant.
The Cumulocity MQTT Service is a new MQTT endpoint implementation for Cumulocity that provides the following benefits:
- Sending and receiving arbitrary payloads on any MQTT topic.
- User-provided microservices can send and receive messages on MQTT topics, and map messages to and from the Cumulocity data model.
- Multi-tenant support with full tenant isolation.
- Bi-directional TLS including authentication with X.509 client certificates.
The MQTT Service does not replace the existing Core MQTT capability of Cumulocity that supports sending device data already in the Cumulocity domain model directly into the platform.
The new capability provided by the MQTT Service allows for easier integration of MQTT devices that cannot use the Cumulocity domain model.
It also supports more flexible communication patterns between devices, applications, and the Cumulocity platform, controlled by user-provided microservices.
Note that in the public preview, MQTT Service clients within a tenant are not isolated from one another.
That is, an MQTT client can subscribe to topic(s) that another client is publishing on, and receive the messages sent by that client.
Full device isolation will be available in the first General Availability release of the MQTT Service.
For more details about this feature refer to the MQTT Service documentation.