The TDatabase Access TagProvider connects to project databases at runtime, enabling data querying without local Tags. Configure this TagProvider to display queried data on TrendCharts and other application areas, enhancing real-time access and utilization of database information within the Unified NamespaceTcpDataAccess TagProvider facilitates the Server to Server communication, allowing two solutions to interact directly with another, exchanging and synchronizing data efficiently. This is especially useful in scenarios where you need to relay data from one system to another without manual interventions, ensuring data continuity and real-time updates.
On this page:
| Table of Contents | ||||
|---|---|---|---|---|
|
Configuration
To set up Database Access as an External Tags sourceTcpDataAccess as a TagProvider, navigate to Unified Namespaces / External TagProvidersNamespace → TagProvider Connections and select the Server to Server Communication.
Connection
parametersParameters
Field | Description |
|---|---|
Provider | Specifies the system the TagProvider will interface with. In this case, it interfaces with Server to Server Communication. |
Access Mode | Determines permissions for interacting with tags. Read allows data reading .For this TagProvider only Read is allowed. Write permits data writing. ReadWrite enables both reading and writing. |
Name | User-defined name for the TagProvider instance. Identifies the specific configuration in the system. |
Description | Explains the TagProvider's purpose or the systems it interfaces with. Provides context for its usage. |
ProtocolOptions | Defines specific communication settings for the connection to the device. |
TagHistorian | Enables the TagHistorian feature for storing historical data. |
TagProperties | Enables the TagProperties feature for managing tag metadata. |
Connection | Defines connection settings for the server, including host, port, username, password, and additional options. |
Station
parametersParameters
The Test button verifies the connection settings to ensure successful communication with the specified server.
Field | Description | |
|---|---|---|
Host | Specifies the IP address of the Server system. It directs the client to connect to the specified server. Example: 192.168.1.1. | |
Port | Indicates the TCP/IP port of the Server system. It allows data transmission via the specified port. Example: 8080. | |
UserName | Identifies the username with ClientStart permission in the Server system. It authenticates the user attempting to access the server. This parameter is optional and defaults to the startup user. Example: admin_user. | |
UserPassword | Provides the password for the user. It secures the connection by verifying the user's identity. This parameter is optional and defaults to the startup user. Example: password123. | |
WindowsAuthentication | Enables Windows-based authentication. It allows users to authenticate using their Windows login credentials. Check the box to enable. | |
CFOrIoTUpdate Write Rate | Enables the configuration mode of the station. CF stands for Compact Framework, optimized for devices with limited resources, while IoT tailors for Internet of Things devices. Choose based on the device type and requirements. Example: Select IoT for an Internet-connected sensor networkSpecifies the frequency at which data updates are written or synchronized with the server. It helps manage bandwidth and ensures timely data relay. Example: 5 seconds. | |
StoreAndForward | Enables temporary data storage if the server is unreachable. It stores data locally and forwards it once the connection is re-established. Check the box to enable. | Update Write Rate | Specifies the frequency at which data updates are written or synchronized with the server. It helps manage bandwidth and ensures timely data relay. Example: 5 seconds
Data Access and Visibility
Not all tags on the remote server will be accessible by the TagProvider. The visibility of the data and its access permissions (read or write) are defined by the remote system, according to the Visibility property of the tags in the remote system.
The available options are:
Private: The tag remains visible only to the local project and its redundant pair. Use this setting to restrict the tag's visibility, ensuring that only the local project and its backup can access the tag. Private tags will not be visible to remote servers using the TagProvider connection.
Protected: The tag becomes visible to external connections for read-only operations. This setting allows external systems to read the tag's value without permitting any modifications, ensuring that the data remains unchanged. Protected tags are accessible to TagProvider connections for read-only operations.
Public: The tag becomes visible to external connections for both reading and writing. This setting provides full access to the tag, allowing external systems to both read and modify the tag's value. Public tags are accessible by TagProvider for both read and write operations.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|