HistoricalTrendApp and TrendPen configuration

In some cases, in the OMI web client, the TrendPen graphic element and the HistoricalTrendApp OMI ViewApp cannot retrieve historical data. There are two reasons for this:

• The Historian Server node name and port are not set in the application settings file for the proxy server on the WebViewEngine platform.

• The Historian Server does not use the security certificate from the System Management Server. This means the OMI web client does not have a trust relationship with the Historian Server and will not accept data from it.

Perform Workaround 1 to correct the first issue. For the second issue, perform one of the two procedures in Workaround 2.

Workaround 1: Update the application settings file for the WebViewEngine:

1. On the WebViewEngine node, in a text editor, open the file C:\Program Files (x86)\Common Files\ArchestrA\Services\proxyserver\appsettings.json.

2. Find this section of the file:

   "history-data": {

   "HttpRequest": {

   "Version": "1.1",

   "VersionPolicy": "RequestVersionExact"

   },

   "Destinations": {

   "destination1": {

   "Address": "https://localhost:32573/"

3. Change localhost to the name of the node where your Historian Server is installed. If Historian is not using the default port of 32573, also set the correct port number.

4. Save and close the file.

Workaround 2: To fix the security certificate issue, you have two choices:

• Install each Historian's certificate on every remote node that will use the OMI web client. You do not need to shut down or disable Historian to do this, but each node or remote device must have the requisite Historian certificate installed before it can use the OMI web client.

• Change the Historian Server node to use the certificate of the System Management Server. You need to shut down and disable Historian during the change, but this method requires changes only on the Historian Server node.

Decide on the method you wish to use, and follow the appropriate procedure below.

To install Historian certificates on Windows nodes or remote devices

Note: Depending on your organization's network configuration, your IT department may be able to install the certificate on all devices remotely. Users would then not need to perform this procedure.

5. For each web client node, in a supported web browser, go to https://<historian_node>:32573/. (If Historian is not using the default port of 32573, use the Historian port number for your installation.)

6. Select the Not secure message, then, in the dialog box that opens, select Certificate is not valid.

7. On the Certificate Viewer dialog box, on the Details tab, under Certificate Hierarchy, select the line that ends in ... CA. Select Export.

8. Save the Historian certificate to a file. You can place it in any folder and give it any name, but do not change the file type.

9. Install the Historian certificate on your node or device. You can do this either by executing the certificate file you just created, or by using Windows Certificate Manager from the Start menu. Once you have started the process, follow the wizard prompts. Be sure to place the certificate in the Trusted Root Certification Authorities store.

10. Close, and re-open your browser.

    You should now be able to open the OMI web client, start the ViewApp, and see historical data.

Note: For remote devices which use an operating system other than Windows, see the manufacturer's instructions for installing a certificate.

To change the certificate on the Historian Server node

11. On the Historian Server node, use the OCMC to stop and disable Historian:

    1. Start the OCMC, and expand the Historian node in the left pane until you see the Historian Server node name.

    2. Expand the node name. Right-click Management Console, select All Tasks, then Shutdown (and disable) Historian.

    3. On the Shutdown and Disable Historian dialog box, make sure the node name is correct.

    4. Select OK.

12. From the Windows start menu, select AVEVA, then Configurator.

13. Under AVEVA Historian, select Server then Rest Configuration.

    The Rest Configuration dialog box opens.

14. For Certificate Source, select Provided by IT.

15. In Certificate, select <hostname> ASB, where <hostname> is the name of the node where your Historian Server is installed.

16. Select OK, then select Configure.

17. Select Close to close the Configurator.

18. In the OCMC, restart Historian:

    5. Expand the Historian node again.

    6. Right-click Management Console, select All Tasks, then select Enable (allow to run) Historian.