Configure advanced settings

Update the Advanced Settings section to specify settings related to the Historian connection.

1. Under Connection, you can specify the TCP Port. The TCP port on the Historian Server node to which history data will be sent. The TCP port is configured when the Historian Server is installed. The default port is 32565. The Default Historian TCP port is configurable and is used for data replication and communication with remote IDAS version 2023 R2 and later (which implies gRPC communication).

   Note: The classic Historian TCP port 32568 which supports WCF communication, was used for data replication and remote IDAS communication with Historian versions 2023 and earlier, and remains for compatibility with previous versions. The default port number for applications created in InTouch HMI 2023 and earlier is 32568. During upgrade, the TCP Port of the migrated application will be automatically updated to 32565. However, if you have manually modified the port number, the modified port number will be retained in the upgraded application.

2. Under the Bandwidth Optimization section, you can select the Enable compression checkbox. Once selected you can specify:

   • Throttling network bandwidth: Specifies limit of bandwidth usage, in kbps, for network communication used by HCAL when communicating with the Historian. A value of 0 disables this feature (default). For more information on estimating your bandwidth needs, see the performance and sizing recommendations for the Historian Server in System Platform Installation. The allowed values are 0 kbps to 65535 kbps.

   • Wait to send incomplete packets: Specifies the maximum time, in milliseconds, for keeping a partially-filled Historian Client Access Layer (HCAL) buffer before sending it to the Historian Server. If the buffer is full, then it is sent immediately, regardless of any value configured in this field. If you have fast-changing data, this setting is irrelevant. If you have slow-changing data and limited network bandwidth, you might want to increase this value so that you have less "chatter" on the network. The allowed values are 1000 milliseconds to 30000 milliseconds.

3. Under the Data Management section, you can specify:

   • Pre-processing buffer size: The total size, in MB, of all buffers used by Historian Client Access Layer (HCAL). The default and minimum value is 8. If you have very high data bursts, then you should increase this value. If this is too low, data loss occurs and error messages related to buffer overflows appear in the Logger. Increase this value in increments of 10 MB. The allowed values are 8 MB to 65535 MB

   • Store forward threshold: The size, in MB, of free space to reserve on the HCAL store-and-forward disk. The space designated will not be used during store-and-forward. This value cannot be a negative number. The allowed values are 0 MB to 65535 MB

   • Store forward minimum duration: The minimum duration, in seconds, for HCAL to function in store-and-forward mode. HCAL will function in store-and-forward mode for this length of time even if the condition that caused HCAL to function in store-and-forward mode no longer exists. The allowed values are 30 seconds to 3600 seconds.

   • Select the Reconnect as soon as possible and do not mark disconnects checkbox: Specifies how trends appear during communication disconnects between Application Server and Historian. It does not affect how trends of history data appear after communications have been restored. If TRUE, no gap will appear in client-side trends for the disconnect interval. While disconnected, the interval is filled in with the last-received value before the disconnect. If FALSE, a gap will appear in client-side trends for the disconnect interval. NULL values are injected on disconnect to create the gap. In both cases, after reconnect, the interval will be filled in with store-and-forward data.

   • Select the Use trusted connection checkbox: Ensures only secure communication with the Historian Server.
     The Use trusted connection checkbox is enabled by default for all new and migrated applications

     • When the Use trusted connection checkbox is selected, only trusted connections will be able to communicate with the Historian server. If there are no common certificates between Client and Historian Node, the connection will fail.

     • When the Use trusted connection checkbox is not selected, a connection to Historian will be established, even when there are SSL errors in the logger.

       Note: We recommend you to configure SMS in the Configurator along with selecting this checkbox to ensure a secure connection.

4. Select Save.

Services to support WCF and gRPC communication

Ensure the following services are running to support backward compatibility when the Historian version is 2023 R2 or higher.

• aahClientAccessPoint (WCF communication) - Supports clients of versions 2023 and earlier.

• aahClientAccessPointNG (gRPC communication) - Supports clients of versions 2023R2 and higher.