Known issues - AVEVA OMI 2023 R2 Patch 01

IMS 2918856

Note: This is an update to information found in the System Platform 2023R2 Readme file.

If the Trend Pen graphic element and the HistoricalTrendApp OMI ViewApp cannot retrieve historical data in the OMI web client, the reason may be that the Historian Server node name and port are not set in the AppSettings.json file on the node hosting the WebViewEngine. Unless the Historian Server is on the same node as the WebViewEngine, you must define the Historian Server system name and port number in AppSettings.json. Follow the procedure below.

IMPORTANT: You must follow these steps even if you already did so before installing the patch. Because we have added support for multiple Historian Servers to the web client, the format of the AppSettings.json file is changed in Patch 01. An AppSettings.json file from the 2023R2 release will not work with 2023R2 Patch 01.

For your reference, the patch installation makes a copy of the existing AppSettings.json file with a .bak extension. Do not just rename or copy this file for use with Patch 01. Because of the file format change, it will not work.

1. On the node hosting the WebViewEngine, make a copy of the file C:\Program Files (x86)\Common Files\ArchestrA\Services\proxyserver\appsettings.json for safekeeping. Then, open the original file in a text editor.

2. Find this section in the file:

   //"history-data-{serverName}": {

   //  "clusterId": "history-data-{serverName}",

   //  "CorsPolicy": "customPolicy",

   //  "Match": {

   //    "Path": "/history-data/{serverName}/{**catch-all}"

   //  },

   //  "Transforms": [

   //    {

   //      "PathRemovePrefix": "/history-data/{serverName}"

   //    }

   //  ]

   //},
   
   //"history-data-{serverName}": {

   //  "HttpClient": {

   //    "DangerousAcceptAnyServerCertificate": "true"

   //  },

   //  "HttpRequest": {

   //    "Version": "1.1",

   //    "VersionPolicy": "RequestVersionExact"

   //  },

   //  "Destinations": {

   //    "destination1": {

   //      "Address": "[https://https://{serverName}:32573/"

   //    }

   //  },

   //  "UseDefaultCredentials": "true"

   //},

3. Make two changes to this section:

   1. Uncomment the section by removing the // at the beginning of each line.

   2. Change each instance of {servername} to the server name of the Historian Server node. There are six, shown in bold in the sample above.

4. If you want to define more than one Historian Server so that users can choose the one they want at runtime, copy this section and change the server name to the one for the additional Historian. Repeat this as needed.

5. Save your changes and close the file.

   Note: This is only one possible cause of failure for the HistoricalTrendApp and the Trend Pen element in the OMI web client. It may also be due to a security certificate issue. See the description of IMS 2918856 in the "AVEVA OMI Issues" section of the System Platform 2023 R2 Readme file for more information and the workaround steps for the security certificate issue.

IMS 3057574

Changes made to an element style (for example, adding an animation or changing the line color) are not reflected when an OMI ViewApp is opened with the web client, even if the ViewApp is redeployed, The changes do appear in the desktop client.

Workaround: Undeploy and redeploy the OMI VIewApp.