Integrating Device Data from Offline Channel


By creating an offline message integration channel, users can import the historical data from a third-party system to EnOS for processing, storing, and computing based on your policies.


To allow the data from a third-party system to be integrated to EnOS, you must create an offline message integration channel for the third-party system. After the historical data has been integrated into EnOS through the offline message integration channel, that data can be used by applications by calling EnOS APIs. Alternatively, the data can also be sent to Kafka topics as offline data based on pre-defined rules. EnOS data asset management functions can then use that data by subscribing to the topics.

Before You Start

Procedure

  1. Select Device Management > Message Integration.

  2. Select New Channel.

  3. Enter the following information in the New Message Channel pop-up window.

    Fields Description
    Integration Mode Required. Refers to the type of data that you want to integrate from a third-party system.
    Channel Name Required. Supports Chinese characters, upper and lower cases, numbers, and underline (_). 4 to 32 characters. The channel name must be unique within this OU.
    Protocol Required. Refers to the protocol used for third-party offline message integration. Currently supports MQTT.
    Target Product Required. Refers to the product which the integrated data belongs to. Every product only supports one offline message integration channel.
    Data Format Required. Refers to the format of third-party offline message. Supports JSON and custom format (pass-through). It is auto-filled when you select the target product.
    Description Optional. Supports Chinese characters, upper cases and lower cases, numbers and underline (_). Maximum up to 100 characters.
  4. Select Confirm to complete the creation of the message channel.

Results

In Device Management > Message Integration, you will be able to view the successfully created offline message channel.