Add a data source

How it works

You can configure a Data Forwarding parser in IoT Platform to forward data from a data source (device messages) to a data forwarding destination, such as another topic, an AMQP server, or another Alibaba Cloud service. This enables communication between devices, between devices and servers, and between devices and Alibaba Cloud services.

Add a data source

1. Log on to the IoT Platform console.

2. On the Overview page, find the instance that you want to manage and click the instance ID or instance name.

3. In the navigation pane on the left, choose Message Forwarding > Data Forwarding.

4. On the Data Forwarding page, click Go to New Version in the upper-right corner.

   Note

   If you have performed this operation before, you are automatically redirected to the new version of the Data Forwarding page.

5. Click the Data Source tab, and then click Create Data Source.

6. Enter a name and description for the data source, and then click OK.

   The name must be 1 to 30 characters long and can contain Chinese characters, Japanese characters, letters, digits, underscores (_), and hyphens (-). A Chinese or Japanese character counts as two characters.

   After the data source is created, the console redirects you to the Data Source Details page. On this page, you can click Edit to modify its name and description, or click Add Topic to add message topics.

7. On the Data Source Details page, click Add Topic. In the dialog box that appears, select the message topics to process and then click OK.

   For more information about the supported topics, see Data formats.

   Important

   For open source MQTT-hosted products and devices, and cloud gateway products and devices, you can select only Custom, Device Status Change Notification, and Device Lifecycle Change topics. For more information about message forwarding topics and data formats, see Messaging for devices that use open source MQTT, Messaging for devices that use JT/T 808, Messaging for devices that use GB/T 32960, and Overview of the SL 651 protocol.

8. Optional: Repeat the previous step to add more message topics to the data source.

   After adding topics, you can manage them on the Data Source Details page. The list shows all configured topics, such as TSL Data Reporting (Topic path: /<productKey>//+/thing/event/property/post) and Device Status Change Notification (Topic path: /as/mqtt/status/<productKey>/+). To remove a topic, click Delete next to it.

9. Optional: Repeat Steps 5 to 8 to add more data sources.

Related APIs

FAQ

• I have configured an ApsaraMQ for MNS server-side subscription, but when I send a message from the console, the queue in ApsaraMQ for MNS does not receive it. Why?

• How can I determine the source topic of a message received by the ApsaraMQ for MNS server?

• How do I implement device connection and status synchronization on IoT Platform?

• How can I notify an app or a mini program after a device goes online?

• After I use an AMQP server to subscribe to messages reported by devices, why can't I receive messages from RRPC topics?

• Can I use an AMQP server to subscribe to hexadecimal data reported by devices?

• Can I export the data reported by devices?