Externally Routing Data
To route data externally, follow these steps:
1. Create a Queue Provider entity. For more information, see Configuring a Queue Provider Entity.
a. Create the Queue Provider entity and choose the package that relates to your external messaging system, such as Azure Event Hubs or Apache Kafka.
b. Configure the Queue Provider entity.
 |
The Configuration tab will be available after saving the entity for the first time. After that, the connection to the external messaging system must be established before saving the entity.
|
c. Activate the Queue Provider.
|
|
The Queue Provider can only be active if the configuration setting is set and connected successfully.
|
d. Create queues.
Use the addQueue() service to create queues. For more information, see Queue Provider Services.
A queue corresponds to a Kafka topic or Event Hubs in ThingWorx.
2. Create an IoT Stream entity. For more information, see IoT Stream.
a. Create IoT Stream entities.
b. Associate them with a queue. You may use the default Queueprovider. Each queue is linked to one IoT Stream and vice versa.
c. Activate the IoT Stream.
3. Externally route the desired property. In the Thing’s property panel, associate the IoT Stream with a property. For more information, see the Configuring an IoT Stream with Thing Properties section in Creating an IoT Stream.
Migrating Entities Between Environments
Queue provider entities and their associated IoT Stream entities can be migrated between different systems, such as from development to production. Follow these steps to migrate existing entities and data from your current Queue Provider environment to a new Queue Provider environment:
1. Export entities from the source system.
2. Import entities into the target system. You may choose to use the default Queue Provider in the target system.
3. In the target system, manually update the Queue Provider with the necessary information.
Related Topics