Upgrade to version 2​.x

If you are upgrading your connector, follow the installation procedure as described in Install the connector paying special attention to the following:

Note: This version of the connector does NOT support a direct upgrade from version 1.x.

If you have a version 1.x of PI Connector for OPC UA installed on your computer and you want to install version 2.x on the same machine, follow these steps:

1. Copy these two files from the existing installation of the PI Connector for OPC UA ver 1.x to a safe location:

   %PIHOME64%\Connectors\OpcUa\Configuration\Datasource.config.json

   and

   %PIHOME64%\Connectors\OpcUa\Configuration\PIServers.config.json

2. Manually uninstall version 1.x.

3. Rename the PI AF database that stores the elements and templates created by version 1.x. The new version will recreate the PI AF structures during the very first start-up.

4. Install and start configuring the new connector.

   Note: The two .json files referenced above contain the Data Source Names and PI Server destinations, which you may want to preserve.

5. During the configuration, leave markers for Create root element and Prefix points checked; see Specify destination settings in the PI Connector Administration user guide for additional information.

6. Naming your registered connector "OPC UA" allows you to reuse your existing PI point names so that the new PI AF structure will look the same as that which was created with version 1.x. The name you entered will appear as the RegisteredConnectorName part of the PI point name mentioned in chapter Naming conventions.

   Note: If you chose some other name than OPC UA while registering the connector to PI Data Collection Manager, then this registered name will be used as the root element in PI AF, and the connector will create a new set of PI points prefixed with it.

The new features in version 2.x include manual or rule-based selection of the actual OPC UA objects and variables, and the option of renaming PI points before they get created. Version 2.x supersedes the filtering based on OPC UA types that was used in version 1.x. Version 2.x does not offer an automated procedure of translating the filter file used in version 1.x to the new selection scenario.