Connecting an Azure IoT Hub Connector and an eMessage 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 or eMessage Connector because the Connectors check for the existence of the ConnectionServicesHub Thing on startup.
Problem Statements: A ThingWorx Platform, v.8.4.0, has been deployed with a ThingWorx Azure IoT Hub Connector, v.2.0, and its related Extension. The ThingWorx Axeda Compatibility Extension needs to be deployed to support the eMessage Connector, v.1.2.2, using the same ThingWorx Platform.
The steps to make this deployment work follow:
1. Back up existing entities created using the Thing Templates of the Azure IoT Extension.
2. Remove the Azure Extension v.2.0 and the related entities. The entities would include the AzureIotThings as well as the AzureIotHub Thing.
3. Remove the Connection Services Extension (CSE), v.1.4.2, that was installed with v.2.0 of the Azure Connector.
4. Install the following components of the Axeda Compatibility Package, v.1.2.2, in the following order:
a. Connection Services Extension (CSE), v.1.5.6
 |
The important part of this installation is to install the new CSE first.
|
b. Remote Access Extension (RAE), v.1.0.2
|
|
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, v.3.0.43