Fine-Tuning the Azure IoT Hub Connector
To fine-tune the Azure IoT Hub Connector, you can make changes to your configuration file. Note that changes do not take effect until the Azure IoT Hub Connector is restarted.
Adjusting the Transport Settings
The transport.websockets group of the configuration file supports not only the address of your ThingWorx Platform, but also timeout settings for authentication and other types of requests. If necessary for your environment, you can add and change the properties for the number of Netty IO threads, the number of Netty bytes channels, and the timeout for each channel.
In the transport.websockets group of the configuration file, you might need to tune the following properties:
1. The amount of time in milliseconds before an authentication request to ThingWorx times out. The default value, shown here, is 10000 ms (10 seconds):
authentication.timeout.ms = 10000
2. The amount of time in milliseconds before requests to ThingWorx that are not for authentication time out. The default value, shown here, is 10000 ms (10 seconds):
request.default_timeout.ms = 10000
3. The number of Netty IO threads. Change this value only if you know that it is necessary for your environment. The default value, shown here, is 8:
iothread.count = 8
4. The number of Netty bytes channels to create for communications with ThingWorx. Change this value only if you know that it is necessary for your environment. The default value, shown here, is 5:
connections.pipe-count = 5
5. The time in milliseconds before each channel times out while trying to connect to ThingWorx:
connections.timeout.ms = 10000
6. Save the configuration file and restart the Azure IoT Hub Connector.