The DataHub 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 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 solution deployment follows this workflow:
- Server 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, enable "Publish to DataHub Service," and inform the IP Address configured on the 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.
In this section: