MQTT
This Micro-Integration enables the flow of messages both from an MQTT broker endpoint to a PubSub+ endpoint and from PubSub+ to MQTT.
MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). It is designed as an extremely lightweight publish/subscribe messaging transport that is ideal for connecting remote devices with a small code footprint and minimal network bandwidth. MQTT today is used in a wide variety of industries, such as automotive, manufacturing, telecommunications, oil and gas, etc.
This Micro-Integration provides 2-way integration configured via “workflows” in your Micro-Integration instance. A workflow is a source-to-processing-to-target data pipeline configured within the Micro-Integration runtime. Each workflow (you can have up to 20 defined per Micro-Integration instance), defines a source, any header processing necessary for the target, and a target destination. When active, events will stream across these Workflows.
Features & Use Cases
The connector is available as:
- A runnable package based on a Java JAR file including a start script
- A container image suitable for running in a container runtime such as Docker or Podman (note this image is not available on Docker Hub at this time. Solace is working on adding it there. In the meantime, there is a download link in the “resources” section of this connector to download the image directly)
This connector is a “self-contained connector” from Solace. All self-contained connectors share a common architecture and provide a number of enterprise services to the connectors such as:
- A local management server accessible over HTTP(s) and JMX exposing endpoints for:
- Health check
- Metrics monitoring
- Log file access
- Workflow adminstration (start & stop workflows)
- A common set of configuration options for:
- logging – log levels, log file size, archive and rollover rules, appenders to export to other log services
- security setup for management endpoints – authentication and authorization to the endpoints, TLS for HTTPS endpoints
- Various runtime deployment options:
- Standalone
- Active_Standby – for redundancy (you can have more than 1 standby instance)
- Active_Active – for horizontal scaling (where the source of data will support multiple active consumers such as a non-exclusive queue in PubSub+)