Server

To configure Server settings

1. On the left navigation pane, expand AVEVA Historian, and select Server.

   

2. Under Database Information, specify the SQL Instances, Database Path and Data Path.

   • SQL Instances
     Name the SQL Instance associated with this historian.

   • Database Path
     Unless you have specific requirements, keep the default SQL Server database path. The default is tied to your SQL Server installation and is the path where the configuration database is deployed. If you need to change the default path, select the ellipsis button to specify a different directory in which to install the historian database files.

3. Under Existing Database Conflict, read the notices, if any.
   If the database is created for the first time, then this option is not available. When reconfiguration is done, then the Drop and Create New Database option is available. If you select this check box, then the existing database is dropped and a new database is created. If this check box is cleared, then the database is not dropped, but configured for changes, if any.

4. Under Alarms and Events Storage, configure how you want to store alarm and events.

   Important: If you want to change this setting later after the Historian is running, you must first shut down and disable the historian using the Management Console. Then, after making the change, you can restart and enable the historian.

   • High-speed (default/recommended)
     The high-speed setting for storing alarms and events in history blocks provides several advantages. You can manage the data using simple operations such as moving, copying, or deleting folders, instead of using database management software. With this storage method, you no longer need to purge to sustain storage. This method offers significantly higher storage rates. Also, the capacity for alarm and event storage is only limited by disk space, not by insertion rate.

   • Traditional
     The traditional setting stores alarms and events in the A2ALMDB SQL Server database. This works well for smaller applications. Alarm and event data stored in the A2ALMDB database can be retrieved using SQL queries. You can also use SQL Server tools, such as Reporting Services, to query alarm and event history.

5. Under Network, accept the default Historian TCP ports or change these settings. The ports you specify are added to the exclusions list of Windows Firewall. You must manually add these ports as exclusions if you use another hardware or software firewall.

   • TCP Port (Classic) is used for receiving data from another system using Historian version 2023 or earlier. If you are sending data to Historian from an Application Engine, Remote IDAS or from another Historian, you must specify this port as part of the connection settings on those source systems.

   • TCP Port is used for receiving data from another system using Historian version 2023 R2 or later. If you are sending data to Historian from an Application Engine, Remote IDAS or from another Historian, you must specify this port as part of the connection settings on those source systems.

6. Select Allow secure connections only to prevent connections to any systems that aren't connected to the System Management Server.

7. Select Rest Configuration to configure remote access to the Historian REST API and Historian Client Web. The Rest Configuration dialog displays.

   

   To configure the HTTPS connection, a certificate is required. You can use a certificate provided by your IT department, or you can use a self-signed certificate generated by the configurator.

   1. To use a certificate provided by your IT department, select "Provided by IT (import / select)" as the Certificate Source.

      • If the certificate is already installed on the system, select the appropriate Certificate from the list.

      • If you have been provided with a certificate but it is not yet installed on the system, select Import.... The Import Certificate dialog displays.

        

        Select to browse and select the certificate file, which has a .pfx file extension.

      • Select the Certificate Store in which to save the Certificate, as directed by your IT department.

      • Enter the Certificate password and select OK when all the information is correct.

   2. To use a self-signed certificate, select "Automatically Generated" as the Certificate Source. The name of the Certificate is automatically selected for you and cannot be changed.

      Using a self-signed certificate makes it easier to configure the server, but it makes the remote browsing experience more complicated. Users will receive security warnings in their browser until the certificate is "trusted" on their system.

      Note: After configuring the Historian with an automatically generated self-signed certificate, when you visit this dialog again, the Certificate Source is "Provided by IT (import / select)". This is because the certificate is installed on the system after configuration, and can now be selected from the Certificate list.

   3. Enter the port numbers to use for the HTTPS Port and the HTTP Port. These ports are used for data queries via Insight or the Historian REST API to the Historian Server.

      Note: To allow the correct functioning of the Alarm Control History Blocks, the firewall must be configured to permit inbound and outbound network traffic on these ports.

   4. The Connections option determines what happens when a connection is made to Historian Client Web over the untrusted (HTTP) port. Select one of the following options:

      • Favor trusted connections, but permit untrusted connections. When this option is selected, users at run time are informed there is a trusted connection available, and they can decide whether to use the trusted or untrusted connection. For more information about the run-time options, refer to the Historian Administrator Guide.

      • Require trusted connections (clients must trust this certificate). When this option is selected, if you are using a certificate from a trusted authority, users are redirected to the HTTPS connection. If you are using an untrusted certificate, such as a self-signed certificate, an informational message is displayed that directs users how to proceed. For more information about this message and how users can proceed, refer to the Historian Administrator Guide.

   5. Select OK to accept the selected options, then select Configure to apply any changes to the system.

8. Under IO Server, if you have multiple Historian nodes, enter a unique Scope that isn’t used by another node. This label is used by network clients such as AppServer and InTouch to identify specific Historians when there are multiple Historian nodes.