![background image](http://html.mh-extra.com/html/sick/tdc-b100/tdc-b100_operating-instructions-manual_1264311023.webp)
SYSTEM DESCRIPTION
3
23
8021804/2017-11-27|SICK
Subject to change without notice
T R A N S L A T I O N O F T H E O R I G I N A L I N S T R U C T I O N S | Telematic Data Collector
3.3
Interfaces for integration into customer applications
The system solution supports the integration of recorded sensor data into all leading
business applications (ERP, CRM OMD, BI, etc.).
There are two options available for integration, which is possible regardless of whether
the SICK online portal or a cloud-based customer server is used.
Transferring data from the SICK cloud via an API
If the SICK online portal is used to process and visualize the sensor data, the data can
be transferred directly from the SICK online portal to a customer application. The data is
transferred via a programming interface (API) included in the scope of delivery.
This programming interface grants access to the software logic of the SICK online portal,
allowing files and content to be processed further among different programs.
Communication with the API uses the
REST
standard protocol in XML data format.
Fig. 13: Transferring data from the SICK cloud to a customer application via an API
For further information on the methods used with the API, refer to Chapter
Transferring data to a customer application using an API interface.
Accessing data from the TDC device via MQTT
If a customer's own server is used instead of the SICK online portal, it is not possible to
transmit the sensor data directly from the TDC device to the server. Data can only be
accessed using the MQTT interface.
MQTT is a special publish-subscribe-based messaging protocol. Here
topics
are set up by
the user, which are then used by clients (in the role of a publisher) to prepare messages
and by other clients (in the role of a subscriber) to receive messages.
On the basis of this principle, communication takes place via a central hub known as the
MQTT message broker. Each message sent by a client includes a
topic
with the data.
Every MQTT client that wants to receive messages for the topic must subscribe to them
through the message broker.
Whenever there are new messages, interested clients will be notified by the broker,
ensuring efficient communication with the subscribers. However, the individual clients are
only familiar with the message broker and not the other subscribers.
Note