Real-time Message Integration¶
Users can import the real-time data reported by the devices in third-party systems into EnOS through real-time message integration. Users can also set the policies to process, store, and compute the integrated data.
The real-time message integration supports the integration of file-type data. Specifically, it supports not only transferring data from the device to EnOS, but also downloading files from EnOS to the device and deleting files stored on EnOS.
EnOS provides real-time message integration APIs, which can be used to integrate the data of measurement points, attributes, and events reported by the device in real-time. Similar to the EnOS APIs, these APIs also use the service account (SA) and access token for authentication.
Message Source Type¶
The real-time message integration currently supports the third-party systems as clients to import historical data and offline cache data to EnOS through the following protocols, formats, or methods.
HTTP. See HTTP Protocol-based Message Integration (Real-time Messages) for the HTTP protocol version, authentication method, and message integration API instructions for real-time message integration.
Process Overview¶
Based on the HTTP protocol, the process for integrating the real-time data of the devices connected to third-party systems into EnOS is as per the below.
Create models and products in EnOS.
Create devices on EnOS in advance from which the real-time messages need to be imported.
Register an application in the EnOS Management Console > Application Registration page, and get its SA, including the following parameters:
AccessKey
SecretKey
Authorize the SA in the Identity and Access Management > Service Account page.
Make the corresponding configurations on the device connected to the third-party system to invoke the real-time integrated API.
The device invokes the API to initiate a request which can carry file-type data to EnOS. The device can also request to download or delete the files stored on EnOS.
EnOS will verify the SA carried by the device. After the verification is done successfully, the data (including files) uploaded by the device will be saved, or the binary data flow of the files to be downloaded will be returned, or the files under the specified path will be deleted.
Note
For the files uploaded by the device, you can also view, download, or delete them in the Device Details page under File after navigating to Device Management > Device Assets or Logical Assets in the EnOS Management Console.
Application of Real-time Messages¶
Once the real-time messages from the third-party systems are integrated into EnOS, the application can invoke these data through the EnOS API. For more details, refer to the API related documents.
Users can also subscribe to the real-time message data flow on EnOS, and the data will be distributed to the corresponding Kafka topic through the rule engine, which can be invoked by EnOS data asset management related functions.