The Hub for Server Communication TagProvider 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:
To configure the Data Hub Service as a TagProvider, navigate to Unified Namespace → TagProvider Connections and select the Hub for Server Communication option.
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. |
Functional Specification
Definition | A TagProvider that facilitates runtime data access and exchange. It operates as a hub, aggregating and distributing namespace information across multiple solutions. |
Purpose | Enables real-time and historical data retrieval from multiple runtimes. Supports unified access to tag values, alarms, and server states across distributed systems. |
Functionality | Provides a centralized connection for accessing runtime data. Manages namespace visibility based on access levels. Supports alarm status retrieval, acknowledgment, and trend history. |
Application | Used in environments where multiple runtimes need synchronized data access. Configured at startup with alias, host, port, and access key settings. Accessible through TCP communication. |
Configuration | Requires defining a listening port, access key, and access mode. Runtime solutions must enable "Publish to DataHub Service" and specify connection parameters, including alias and host settings. |
Usage | Users configure the runtime to publish data and connect to the hub. Clients query namespace data using the defined access levels. Alarm interactions and tag updates occur through read/write operations. |
In this section: