Upgrading to Version 2​.3​.2

This section provides an overview of tasks that need to be completed if you want to upgrade to version 2.3.2.

To upgrade to version 2.3.2:

1. Go through the System Requirements and make sure all the requirements are met.

2. Install the 2.3.2 version of the Service. See Install AVEVA Integration Service for more information.

3. Configure SSL Certification.

   1. Obtain a certificate from a verified certificate provider.

      Note: You can also use a self-signed certificate, but a self-signed certificate is not recommended because of the security risks associated with such certificates. If you decide to use a self-signed certificate, you must be knowledgeable about how to create and configure them. The self-signed certificate must also be added to the Trusted Root Certificate Authorities.

   2. Bind the certificate to the Service. To bind the certificate:

      1. Open Internet Information Services (IIS) Manager, locate and select IntegrationServiceConfigAPI.

      2. In the Actions pane, click Bindings in the Edit Site area. The Site Bindings dialog box is displayed.

      3. Select the row with port number 60920, and click Edit to edit the information. The Edit Site Binding dialog box is displayed.

         

      4. Make sure your certificate is specified and selected in the SSL certificate list.

         Note: You can modify the other settings in this dialog box according to your requirements.

      5. Click OK to save the changes. Your certificate is now configured to the Service.

4. In the Services window, locate AVEVA Integration Service and log on using Service account. For information on logging on a Service user, see the Starting AVEVA Integration Service Using a Service Account section in the AVEVA Integration Service Setup Guide.

5. Open Integration Settings Editor. Modify the Datasource Store URL according to how you have configured it. The URL must be in the following format: https://<hostname.domain>:<port number>/.

   

6. Click Connect.

7. After successful connection to the Datasource Store, click Start to start the Service.

   Before the Service is started,the following actions are performed:

   Note: Starting with version 2.3.2, the Service requires all datasource names to be unique. They must also not contains special characters other than space, - (hyphen) or _ (underscore). This is because the data sources are now stored in a database instead of a text file, and are referred by name rather than internal ID by the client software.”

   • If the data sources names are unique and do not contain prohibited special characters, the data sources are migrated to the Datasource Store, and a message stating that the data sources are successfully migrated is displayed.

     

   • If the data source names are not unique and/or contain prohibited special characters, a dialog box prompting you to change the required data source names is displayed.

     

     The migration is not completed until all the data source names are unique and do not contain the prohibited special characters.

     

     After you have changed the required data sources names, the data sources are migrated to the Datasource Store and a message stating that the data sources are successfully migrated is displayed.

8. After successful migration, the Service is started, and is ready for use.

   Note: After upgrading to version 2.3.2, the Service must always be started from Integration Settings Editor only.