Requests from the machines (RequestNotifications) are transferred to an internal and protocol-independent format, serialized to JSON and sent to the desired endpoint. The procedure is shown in the figure below. Six endpoint types are supported:
Broker for AMQP 0.9 \ It is possible to send the DDL messages to a messaging broker if this uses AMQP 0.9. These messages are sent to the exchange configured for the respective broker (e.g. RabbitMQ).
AMQP 1.0 Messaging Queue It is possible to send messages to queues if these queues use AMQP 1.0. These messages are sent to a messaging queue that is specifically configured to receive DDL messages (e.g. Universal Messaging).
KAFKA broker DDL messages can be sent to Kafka brokers. The messages are sent to specific topics that are specifically configured to receive DDL messages.
REST services REST services are accessible via an HTTP connection to the corresponding URI. Messages can be retrieved there and processed further from there.
Solace Broker From DDL V5.2 onward, it is possible to send the standard notification service JSON message and/or raw messages from the machine (XML or DAT) to a Solace broker using the native Solace client library.
Azure IoT Hub From DDL V5.14 onward, it is possible to send DDL messages to an Azure IoT Hub. By default, AMQP is used as the communication protocol for sending messages. However, this is configurable. Communication via MQTT or HTTP is also supported.
