Send data to Data Publisher

Data Publisher can process messages in JSON format.

The message structure should follow the Industrial Application System’s messaging specifications, but it does not have to. If this is not the case, Data Publisher will embed the original message as "payload" object of the message structure defined in the Industrial Application System’s messaging specifications.

Currently, Data Publisher checks the tenant id of the message using the property "ownerId" of the "payload" object (which has to match the tenant of the processing chain). If this is missing, the message will be skipped and a log entry will be created at debug level.

Modules send messages to Data Publisher through the internal RabbitMQ message broker.

The exchange name which the messages are sent to is specified for each data type during module registration (see Getting started for details)

DataPublisher is authorized to consume messages from exchanges starting with "x.nexeed." or "x.datapublisher.". So if the exchanges used by the modules to publish their messages follow this naming convention, Data Publisher will be able to consume them automatically. Otherwise, the operator will have to adjust the permissions of Data Publisher on the exchanges via the RabbitMQ management UI.