ThingWorx Azure IoT Hub Connector for Microsoft Azure Industrial IoT (IIoT) for OPC UA > Step 8. Creating the Industrial Gateway and IoT Edge Things for Telemetry
Step 8. Creating the Industrial Gateway and IoT Edge Things for Telemetry
As long as you have created the AzureIotHubTemplate Thing and the AzureIotThings in ThingWorx, completed the configuration of the Connector and have it, the Azure IoT Hub, and your devices running and connected to ThingWorx, you can use ThingWorx Composer to monitor the nodes of your OPC UA server.
This section provides a quick walk-through of the steps For detailed instructions, refer to Industrial Connections.
1. From the left navigation pane in ThingWorx Composer, select Browse > Industrial Connections. You should see your endpoints listed in the right panel.
2. Click the name of the endpoint that you are interested in. If you only have one OPC UA endpoint at the Edge, it should be the only endpoint listed here.
3. Once you select an endpoint, a temporary Industrial Thing is created. To make this Thing permanent, click Save. This is your Industrial Gateway Thing.
4. On the newly created Thing go to the Discover page
5. Navigate to your nodes using the tree view. If you cannot browse, you may need to set user permissions for the Industrial Gateway Thing. The next section explains how.
6. Select the nodes, then click Bind to New Entity. In the popup window, select RemoteThing.
7. The basic properties of the Thing should be created for you. Next to the Save button, check the To Do page to see what needs to be done before the Thing can be saved and persisted. When you have completed the tasks, click Save to persist the Thing to the database.
8. On your newly created Remote Thing go to the Properties page. You should see your properties receiving telemetry.
Batched Telemetry
Batching telemetry has the benefit of reducing the number of device-to-cloud (D2C) messages, but has the drawback of increasing the latency of data to ThingWorx Platform. Batch processing comes by default with the ThingWorx Azure IIoT OPC UA integration. You do not have to do any additional configuration. The publisher module of the IoT Edge Runtime sends batched/bulk telemetry where multiple messages are batched together before being sent to Azure IoT Hub.
If the number of messages is one or two, batching can go more slowly than if you sent them individually. You may want to test the speed by sending one property, then two or three properties and process them at a faster interval. For example, if the interval is 10 seconds, updates do not appear right away.
If you want to override the default values for batching telemetry, you can configure batch sizes and update batch timing in the aiiot-common-values.yaml file for the Publisher component of the Azure Industrial IoT (IIoT) Microservices. Here is an example from that file:

enabled: true
value: "10000"
VALUE: "50"
This configuration of the publisher sets batch sizes of no more than 50 property updates with updates "batching" for no longer than 10 seconds (10000 milliseconds).
Once you have updated the yaml file, you need to upgrade the AKS microservice for the Publisher component of the Azure IIoT Microservices, using the following command:

helm upgrade --install aiiot --namespace aiiot .\Industrial-IoT\deploy\helm\azure-industrial-iot\ -f aiiot.yaml
When using the OPC UA integration, the model database will need additional resources, even if data is not persisted. Exhaustion of these database resources with large peaks of traffic, such as the traffic after an outage, will affect ThingWorx performance.
The Azure Industrial IoT GitHub repository has information here about telemetry message batch processing, in the section, "OPC UA Pub/Sub Mode". Samples in JSON and binary encoding are provided.