The DataHub Communication Service is a distributed data aggregation and communication solution designed for large-scale industrial applications. It enables multiple independent applications to publish and consume real-time data, device states, and alarm events through an optimized, subscription-based architecture. In summary, this TagProvider Connection enables multiple runtime solutions to share and access tag, device, server, info, and alarm namespaces. It uses a TCP-based connection, listening on port 30001 by default. Each runtime configures its access through an alias and an optional access key.
On this page:
Configuration
To configure the Data Hub Service as a TagProvider, navigate to Unified Namespace → TagProvider Connections, press the Plus button, and select the Hub for Server Communication option.
Connection Parameters
Field | Description |
|---|---|
Provider | Specifies the system the TagProvider will interface with. In this case, it interfaces with the Hub for Server Communication. |
Access Mode | Determines permissions for interacting with tags. Read allows data reading. Write permits data writing. ReadWrite enables both reading and writing. |
Name | Identifies the tag provider connection. Differentiates multiple connections within the system. |
Description | Provides details about the connection. Helps users understand its purpose. |
Connection | Shows the parameters used for establishing the connection. |
Listening Port | Specifies the port for communication. Directs network traffic through the assigned port. |
AccessKey | Manages authentication for the connection. Protects access based on security requirements. |
Deployment
The DataHub solution deployment follows this workflow:
- Service Configuration: Navigate to Unified Namespace/TagProvider Connections and configure a new connection using the DataHub Service provider, specifying the listening port and access key. This will be the instance to which the client will connect.
- Client Configuration: Navigate to Runtime/Startup/Execution Environment and enable the "Publish to DataHub Service" checkbox option. Click on the gear icon to open the DataHubService Settings dialog, and inform the IP Address configured on the DataHub Service. For detailed information see Publish to DataHub Service.
- Runtime Startup: Both the server and clients must be running. Clients connect and begin publishing data to the DataHub Service.
- Testing: On the solution with the configured DataHub Service, navigate to Unified Namespace/Connection Monitor and check if the Client data is available.
Service configuration
This initial configuration sets up the system’s data exchange foundation, making it possible for multiple clients to communicate with the DataHub Service instance. It requires only navigating to Unified Namespace/TagProvider Connections and configuring a new connection using the DataHub Service provider.
Clients configuration
This configuration enables individual clients to send data to the previously configured DataHub Service instance. This is done by navigating to Runtime/Startup/Execution Environment, where the "Publish to DataHub Service" checkbox must be enabled. After enabling this option, users need to click the gear icon to open the DataHubService Settings dialog. Within this dialog, they must input the IP Address of the DataHub Service instance on the network that was configured in the first step. This ensures that the client software knows where to send data and can establish a network connection. E.g., 192.168.1.100 for local, 34.125.78.210 for cloud, or 10.8.0.5 for VPN.
Runtime Startup
Both the server (DataHub Service) and all configured clients must be running simultaneously for data exchange to begin. The DataHub Service should be started first to ensure it is ready to receive connections before any clients attempt to publish data. After the service is active, each client should be started in sequence, allowing them to establish their connections and begin sending data. Once running, clients will automatically initiate data transmission based on their configured settings.
Testing
The testing stage involves verifying that the DataHub Service receives data from all configured clients correctly. This is done by accessing the Unified Namespace/Connection Monitor and refreshing the connections tree, which allows for real-time data transmission. If client data appears in the monitoring interface, it confirms that the system is operating correctly and that communication between clients and the DataHub Service is functional.
Troubleshooting
Enabling and checking logs on both the DataHub Service and client machines can provide insight into potential misconfigurations or errors. It ensures that the deployed solution is functioning as expected and that all configured components are successfully exchanging data in real time. To check the TraceWindow, open it via Tools in the Solution Designer, access it through Run Tools in Runtime/Diagnostics, or click its icon in the Status tab of the Startup popup.
In this section: