The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Connectivity service | Page | The “connectivity” service enables Ditto to establish and manage client-side connections to external service endpoints. You can communicate with your connected things/twins over those connections via Ditto Protocol messages. The connectivity service supports various transport protocols, which are bound to the Ditto Protocol via specific Protocol Bindings.... |
| Connections | Page | Connection model Note: To get started with connections right away, consult the Manage connections page. You can integrate your Ditto instance with external messaging services such as Eclipse Hono, a RabbitMQ broker or an Apache Kafka broker via... |
| Placeholders | Page | Placeholders Placeholders may be used at several places in Ditto where something should be resolved by a variable. The general syntax of a placeholder is {{ prefix:name }}. Which placeholder values are available depends on the context where the placeholder is used. Scope: Entity creation /... |
| Header mapping for connections | Page | When receiving messages from external systems or sending messages to external systems, the external headers of the messages can be mapped to and from Ditto protocol headers. That way the headers can be passed through Ditto, or defined Ditto protocol headers like for example correlation-id may be mapped to... |
| Manage connections | Page | In order to manage (CRUD) connections in Ditto DevOps commands have to be used. There is no separate HTTP API for managing the connections, as this is not a task for a developer using the digital twin APIs but more for a “DevOps engineer” creating new connections to external... |
| Payload mapping in connectivity service | Page | TL;DRThe payload mapping feature in Ditto’s connectivity APIs can be used to transform arbitrary payload consumed via the different supported protocols to Ditto Protocol messages and vice versa. Motivation Eclipse Ditto is about providing access to IoT devices via the digital twin pattern. In... |
| Connectivity API overview | Page | The Connectivity API is a bare management API for Ditto’s Connectivity Service. It completely depends on DevOps Commands for connection management. Use it to manage client connections to remote systems and to exchange Ditto Protocol messages with those. If a remote system is unable to send... |
| AMQP 0.9.1 protocol binding | Page | Consume messages from AMQP 0.9.1 brokers via sources and send messages to AMQP 0.9.1 brokers via targets. Content-type When messages are sent in Ditto Protocol (as UTF-8 encoded String payload), the content-type of AMQP 0.9.1 messages must be set to: application/vnd.eclipse.ditto+json... |
| AMQP 1.0 protocol binding | Page | Consume messages from AMQP 1.0 endpoints via sources and send messages to AMQP 1.0 endpoints via targets. Content-type When messages are sent in Ditto Protocol (as UTF-8 encoded String payload), the content-type of AMQP 1.0 messages must be set to: application/vnd.eclipse.ditto+json... |
| HTTP 1.1 protocol binding | Page | Perform HTTP request (with verbs POST, PUT, PATCH) to HTTP endpoints via targets. Specific connection configuration The common configuration for connections in Connections > Targets applies here as well. Following are some specifics for HTTP connections: Source format Note: HTTP... |
| Apache Kafka 2.x protocol binding | Page | Send messages to Apache Kafka via targets. Content-type When Kafka messages are sent in Ditto Protocol, the payload should be UTF-8 encoded strings. If messages, which are not in Ditto Protocol, should be processed, a payload mapping must be configured for the connection in order... |
| MQTT 3.1.1 protocol binding | Page | Consume messages from MQTT brokers via sources and send messages to MQTT brokers via targets. Content-type When MQTT messages are sent in Ditto Protocol, the payload should be UTF-8 encoded strings. If messages, which are not in Ditto Protocol, should be processed, a payload... |
| MQTT 5 protocol binding | Page | Consume messages from MQTT 5 brokers via sources and send messages to MQTT 5 brokers via targets. Content-type When MQTT messages are sent in Ditto Protocol, the payload should be UTF-8 encoded strings. If messages, which are not in Ditto Protocol, should be processed, a... |
| Certificates for Transport Layer Security | Page | Verify server certificate Server-certificate verification is available for AMQP 0.9.1, AMQP 1.0, MQTT 3.1.1, MQTT 5, HTTP 1.1, and Kafka 2.x connections. Connection configuration Verifying the server identity mitigates the risk of man-in-the-middle attacks. To have Ditto check the identity of external... |
| Release notes 0.3.0-M1 | Page | Version 0.3.0-M1 of Eclipse Ditto, released on 26.04.2018 |
| Digital twins of devices connected via LoRaWAN to TTN | Post | A workshop of the 2020 The Things Virtual Conference on April 16th 2020 is/was about how to connect Eclipse Ditto to “The Things Network” via TTN’s MQTT broker in order to automatically update digital twins of devices connected via LoRaWAN... |
| Selective push notifications available | Post | The connectivity service supercharged Ditto’s flexibility in integrating with other services. It’s such a great feature to let the other connected services know about thing updates and property changes. Even the direct exchange with real-world assets became more flexible through the multi-protocol support. But with a steady increase in... |
| Connecting Eclipse Ditto to Eclipse Hono | Post | Warning: This guide does no longer work with the latest (1.x) versions of Ditto + Hono. Please take a look and make use of the Eclipse IoT Packages “cloud2edge” package in order to setup and automatically connect Ditto + Hono. With the recently... |
| Ditto's connectivity capabilities are pimped up | Post | It has been quite lately on our website and on GitHub as the Ditto team currently prepares its new connectivity microservice. Until now Ditto’s amqp-bridge service could connect to AMQP1.0 endpoints (e.g. Eclipse Hono). That worked quite well, but still had some issues: failover/reconnection was not... |