Release Notes > ThingWorx Azure IoT Hub Connector Release Notes, v. 4.0.0
ThingWorx Azure IoT Hub Connector Release Notes, v. 4.0.0
The ThingWorx Azure IoT Hub Connector enables devices that use the Microsoft Azure IoT Edge SDKs and IoT Hub Device SDKs to interact with the ThingWorx Platform. Note that ThingWorx Platform running in single-server mode only is supported in release 4.0.0.
Release 4.0.0 adds support for users of the ThingWorx Microsoft Azure Industrial-IoT OPC UA integration to communicate with a ThingWorx Platform. Again, only single-server mode of the platform is supported at this time.
The ThingWorx Azure IoT Hub Connector itself includes the following components:
The core connection server and the Azure IoT Hub Protocol Adapter, configured to support Azure IoT Hubs, Azure IoT Edge Devices and Edge Modules, and Azure Blob Storage Containers connected to an Azure IoT Hub. For users of the ThingWorx Azure OPC UA integration the protocol adapter component translates messages from the OPC UA format into ThingWorx AlwaysOn messages and vice versa.
An Azure IoT Hub Adapter Extension that must be imported into ThingWorx Platform to support Azure IoT entities. This extension provides entities to support Azure IoT Devices and Azure IoT Edge Devices, an Azure IoT Hub, and Azure Storage Containers. For the Azure OPC UA integration, it provides mashups to support the Industrial-IoT entities.
Another extension, called Connection Services Extension (CSE), manages communication between ThingWorx Platform and the Azure IoT Hub Connector.
Together, these components provide the following features:
Scalable connectivity between ThingWorx Platform and Azure IoT Hubs, Azure Blob Storage Containers, Azure IoT Devices and Edge Devices, and the Microsoft Azure Industrial-IoT Stack, OPC UA.
Horizontal scalability by adding instances of the ThingWorx Azure IoT Hub Connector and setting up partitions on an Azure IoT Hub to handle increased load.
A health check service, logging, and metrics collection enable you to monitor the health of the connection to the ThingWorx Platform in either single-server or clustering mode, as well as the traffic that the platform or cluster is handling. The logging feature provides detailed logs to help in troubleshooting.
Configuration file to tune settings for the Connector.
Security for connections to ThingWorx Platform.
All of these components are part of the distribution bundle for the Connector.
What’s New in ThingWorx Azure IoT Hub Connector, v. 4.0.0
Release 4.0.0 of the ThingWorx Azure IoT Hub Connector adds support for connecting OPC/UA servers that connect to the Microsoft Azure Industrial-IoT Microservices to the ThingWorx Platform.
The version of jackson-databind has bee upgraded to 2.10.1 from 2.9.7 for this release of the Connector. The Azure IoT Hub Connector does not enable "default typing".
AZX-601 and AZX-602
The default name of the SCM Module in the Connector has been changed to ThingWorxAzureSoftwareContentManagement. You no longer need to change the name in the configuration file of the Connector. In addition, the name in the marketplace has been updated to match this name.
The shared AES key, azure.connector.key, has been removed from the Azure IoT Hub Connector. You no longer have to encrypt the credentials for the Azure IoT Hub in ThingWorx Platform. The instructions for this step have been removed from the documentation. The workflow diagram that contained this step has also been updated.
AZX-370 (14073360)
Missing information in Azure IoT Hub Connector Jobs demo, step 9. The topic, Device Jobs Demo, has been updated to resolve this issue.
Support for ThingWorx Microsoft Azure OPC UA Integration
Support for Microsoft Azure Industrial-IoT - OPC UA
For more information on the ThingWorx Azure OPC UA integration, refer to ThingWorx Azure IoT Hub Connector for Industrial-IoT - OPC UA .
The Azure IoT Hub Connector Help Center has been updated for changes in the 4.0.0 release, including support for ThingWorx Microsoft Azure Industrial-IoT OPC UA integration..
Configure Endpoint Credentials
Performing UA Command and Control operations require the requestor to present credentials. The new UA Endpoint Management mashup allows the users of ThingWorx Composer to provide the credentials as well as to browse and subscribe for telemetry. For information on Configuring endpoint credentials, refer to the topic, Using ThingWorx OPC UA Mashups to Configure Your OPC UA Applications and Endpoints.
For more information about the Azure IoT Hub features, refer to the Microsoft Azure IoT Hub developer guide at
Issues Fixed in v.3.0.0
In addition to continuous security improvements, this release provides the following software issues fixed in this release:
AZX-485 (14753782)
Azure IoT Hub Connector 2.0.0 works well with Java 1.8_u131 but fails with Java 1.8_201 on Azure Windows 2016.
This issue is fixed in v.3.0.0 of the Connector. The version of Java for this release is 1.8_u141 at minimum due to requirements of the ThingWorx Security Client application.
AZX-372 (14078093)
The Edge Device demo fails to start with error: No signature of method.
This issue is fixed in this release.
AZX-374 (14074993)
Azure IoT Hub Connector Firmware Update Demo NodeJS code fails.
This issue is fixed in this release.
Issues Fixed in v.2.0.0
The following issues are fixed in this release:
AZX-8 (formerly VOL-41)
The Azure IoT Hub Connector disappears from the list of connected Connection Servers on the platform.
When it starts up, the Azure IoT Hub Connector is visible under the list of Connection Servers on the Monitoring tab in ThingWorx. When run continuously under a high load, the Connector disappears from that list after several hours have passed. The Connector also stops processing messages, but no exceptions are written to the logs.
This issue is fixed in this release.
Azure IoT Hubs with uppercase letters in their names will not connect.
With release 2.0.0, the Connector connects to Azure IoT Hubs with uppercase letters in their names.
Azure-cxserver-name does not exist or is not yet associated with a Thing error when starting up the Azure IoT Hub Connector.
The ApplicationLog error that was generated when the Connector Thing did not exist no longer occurs. However, if the bind fails (the Thing exists but does not have the tthcorrect template), the error message about the bind failure is logged.
Allow multiple properties in Cloud to device messaging.
Cloud-to-device messaging sends only one property at a time. Essentially, after a property value changes, a message containing the update is sent.
The ThingWorx Azure IoT Hub Connector now allows multiple property updates to be sent in a single message. Refer to the ThingWorx Azure IoT Hub Connector Installation and Operations Guide, v.2.0.0 for details.
Remove azureHub property from AzureIotHubThing Thing Template.
The azureHub property on the AzureIotThing Thing Template is no longer used and has been removed from this Thing Template.
Known Issue
The following table describes a known issue for this release:
Message ordering is not preserved for a single device.
Although messages are retrieved synchronously from the Azure Event Hub endpoint, messages are dispatched to ThingWorx Platform asynchronously, leading to potential out-of-order application.