Connecting an eMessage Connector and an Azure IoT Hub Connector to the Same ThingWorx Platform
The Connection Services Hub is used to manage event notifications between Connectors and the ThingWorx Platform. You must install it before launching the Azure IoT Hub Connector or the eMessage Connector because the Connectors check for the existence of the ConnectionServicesHub Thing on startup.
Problem Statement: A ThingWorx Platform, has been deployed with a ThingWorx Azure IoT Hub Connector and its extensions, the Connection Services Extension (CSE) and the Azure IoT Extension. The ThingWorx Axeda Compatibility Extension (ACE) needs to be deployed to support the eMessage Connector, using the same ThingWorx Platform.
Solution
The steps to make this deployment work follow:
1. Export existing entities created using the Thing Templates of the Azure IoT Extension. The entities would include the AzureIotThing Things for devices as well as the AzureIotHubTemplate Thing and, if used, the AzureBlobStorageTemplate Thing.
2. Remove the Azure Extension and the related entities from the platform.
3. Remove the Connection Services Extension (CSE) that was installed with the Azure IoT Extension and Connector.
4. Install the following components of the Axeda Compatibility Package in the following order:
a. Connection Services Extension (CSE)
 |
The important part of this installation is to install the new CSE first.
|
b. Remote Access Extension (RAE)
|
|
Since the entities in the Axeda Compatibility Extension inherit from entities in the Remote Access Extension, it is important to install the RAE second.
|
c. Axeda Compatibility Extension
d. ThingWorx Utilities Core and ThingWorx Utilities SCM Extensions
5. Import the Azure IoT Extension and entities.