Phase 2: Install PI Integrator for Business Analytics

Phase 2 involves installing PI Integrator for Business Analytics and specifying the PI AF server and Microsoft SQL Server.

Before you install PI Integrator for Business Analytics:

• Ensure that you have met all the prerequisites in: Phase 1: Prepare to install PI Integrator for Business Analytics.

  Note: Each instance of any PI Integrator product built on the PI Integrator Framework must be installed on its own machine.

1. Log on to the computer where you will be installing PI Integrator for Business Analytics.

2. Download the latest version of the PI Integrator for Business Analytics setup kit from the Customer Portal.

3. Right-click the setup executable and click Run as Administrator to run the installation wizard.

   The Self-Extracting Executable window opens.

4. Specify the extraction path for the installer and click OK.

   The Welcome to the PI Integrator for Business Analytics Setup window opens, listing the separate modules included with the installation. The installation wizard installs each module or ensures that the module already exists on your system.

5. Click OK.

6. If no AVEVA products have been previously installed on this computer, then complete the following steps. Otherwise, skip to the next step.

   1. In the Default Servers window, specify the PI Data Archive server and, optionally, the PI AF Server, and click Next.

   2. In the Installation Directories window, specify the locations for installing AVEVA products. You can either accept the defaults or specify a different location.

      Note: PI Integrator for Business Analytics is installed in %PIHOME64%.

   3. Click Next.

7. In the Welcome to the PI Integrator for Business Analytics Installation window, click Next.

   The Customer Experience Improvement window is displayed

8. In the Logon Information window, select either Virtual accounts or domain user accounts. If using domain user accounts, specify the Username (including domain) and Password for the Windows service account that will run the PI Integrator Framework, PI Integrator Sync, and PI Integrator Worker Node(s) services.

   Note: If the Windows service account is a group Managed Service Account (gMSA), then specify its username in the following format: username$ and omit the password.

9. Click Next.

   The AF Server Connection window opens.

10. Specify the PI AF server on which PI Integrator for Business Analytics will store the view definitions and other metadata.

    In the AF Server field, enter the name or location (IP address) of the PI AF server.

    Note: If you encounter an error, ensure that the user account used to install PI Integrator for Business Analytics is mapped to the Administrators AF identity on the PI AF server.

11. Click Next.

    The SQL Server window opens.

12. Specify the Microsoft SQL Server on which PI Integrator for Business Analytics will store view metadata, statistical data, and PI Integrator for Business Analytics logs.

    Specify only the host name (or fully qualified domain name) if you're using the default instance. If you are using a named instance, specify the host name (or fully qualified domain name) and instance, for example: mySQLserverBA1\PIViewInstance. Using "." is not supported for referring to a local SQL server.

13. Specify how PI Integrator for Business Analytics will be authenticated with the specified Microsoft SQL Server database. Choose one of the following:

    • Windows Authentication (Default)

      The Windows service account user is used as the credentials to connect to the Microsoft SQL Server.

      Note: If you are using a group Managed Service Account (gMSA) or Virtual accounts, then you must use Windows authentication.

    • SQL Server Authentication

      Note: SQL Server authentication is not recommended. Create a login specifically for the PI Integrator Framework service.

      Click SQL Server Authentication to use SQL Server authentication to connect to the specified Microsoft SQL Server database.

      Enter the username and password for the dedicated Microsoft SQL Server user that has the required access to the Microsoft SQL Server.

14. Click Next.

    The Port and TLS Certificate Configuration window opens.

15. Enter a valid available port number in the Enter a port number field and click Validate Port.

    Note: This port is used in a web browser to connect to PI Integrator for Business Analytics.

    Port 80, by convention, is associated with http protocol which is not secure. Since only https is supported (encrypted secure protocol), the use of port 80 is restricted.

    Tip: If you use the default port, 443, you can omit this port number when you specify the URL for PI Integrator for Business Analytics.

16. Choose a TLS certificate from one of the following sources:

    • (Recommended) TLS certificate from a certificate authority. Choose Import certificate and click Select Certificate to choose a certificate that has been issued by a certificate authority and imported to the machine where PI Integrator for Business Analytics is being installed.

    • Self-signed certificate that is generated during the installation. This is the default. Choose Self-signed certificate.

      Note: If you choose this option, users logging in from remote machines may see a security warning message. To avoid this warning for self-signed certificates, the certificate must be explicitly trusted on the client machine. See the workaround in the Knowledge Base article Certificate error returned when navigating to a PI Vision or PI Web API web site using a self-signed certificate.

17. Click Next.

    Note: If you encounter an error, ensure that the port is unused and open.

18. In the PI Integrator Worker Nodes window, click the arrow and select the number of worker nodes you want installed, and then click Next.

    The PI View Deprecated Verification window opens.

    Note: Each worker node requires additional CPU and RAM. For more information on the resources required, see System requirements.

19. The PI View Deprecated Verification step requires you to acknowledge that the PI View target is deprecated. All existing views using the PI View target will be disabled from publishing after the installation.

    • (Recommended) A scan is available to detect any views on your system that use the PI View target. If the scan completes successfully, there will be a list of the view names for detected views, as well as a link to the exported list file in the %PIHOME%\dat directory. You can use this scan to identify PI View views that can be deleted or migrated to the Microsoft SQL Server target as an alternative. For instructions on how to migrate views using the PI View target to Microsoft SQL Server, see Migrate PI View target to Microsoft SQL Server target.

      • If an error occurs during the scan, an error message will appear. Click OK to close the error dialog.

      • If the scan succeeds but the list fails to be exported, please manually take note of the view names.

    Click the acknowledgement checkbox to continue the installation. Click Next.

    The Ready to Install Application window opens.

20. Click Install.

    The Updating System window opens showing the progress of the installation.

21. When the installation is finished, the Installation Complete window appears. Click Close.