A connection in general describes that two parts are linked with each other. In our context, we use the term connection to describe the linking of your Things service instance with other endpoints/servers to integrate them with each other.
You can configure connections to various endpoints:
- Bosch IoT Hub (via Apache Kafka) - the recommended way for device connectivity - bi-directional
- Bosch IoT Insights (via HTTP) - outgoing only
- AMQP endpoints using AMQP 1.0 or AMQP 0.9.1 (e.g. RabbitMQ, Solace, Azure Service Bus) - bi-directional
- MQTT endpoints using MQTT 3.1.1 or MQTT 5 (e.g. Eclipse Mosquitto, HiveQM) - bi-directional
- AWS IoT MQTT - bi-directional
- Apache Kafka
- HTTP - outgoing only
Additionally, any WebSocket connection can be opened ad-hoc but is not stored at the solution, nor is it visible in your list of connections.
To configure a managed connection of your Things service instance with external systems you can use the user interface as described at getting started > booking > manage your connection.
There you can see the status of connections, adjust them, or even create new ones.
When a managed connection is opened or gracefully closed, the Things service can send a respective announcement. The configuration option per connection to activate/deactivate publishing of such announcements is available in the Connections/Integrations UI tab as well as via API.
The Things service provides payload mapping functionality. Thus, you can map incoming messages to Eclipse Ditto conform payload and vice versa.
Find details at https://www.eclipse.org/ditto/connectivity-overview.html.