Install Data Archive

This topic covers Phase 2 of a Data Archive install on your host computer using the PI Server install kit.

By selecting PI Data Archive from the Server Roles tab, the typical features are selected for installation. The typical features included with this server role are PI Data Archive Server, the PI to CONNECT Agent, PI AF Link Subsystem, PI Totalizer Subsystem, PI System Explorer, and PI System Management Tools. For a full list of PI Server components that are not included in a default installation of Data Archive, see Phase 2: Installation.

If you plan to transfer large amounts of data to the CONNECT data services cloud portal using the PI to CONNECT Agent, install the agent on a host computer that is separate from the Data Archive deployment. An Internet connection is required to configure the agent and then transfer data. The PI to CONNECT Agent is not collective aware, and the agent connects to a particular node in the Data Archive collective. For smaller transfers, installing the agent on a single node in the collective is OK, but there is no advantage with installing the agent on multiple nodes in the collective.

Note: If you are setting up a Data Archive collective, follow this procedure on the computer that you intend to be the primary of the collective, first. Next, follow this procedure on all computers that are intended to be secondary computers. Then, to create the collective, see the High Availability topic Create a collective. Finally, configure the collective before you configure any interface nodes for the collective.

1. Download the install kit onto your host computer, and start the install wizard.

   The Welcome screen opens.

   Note: If the required version of .NET Framework is not installed on your computer, a message appears indicating that it is necessary to proceed with the installation. Accept the license terms to install .NET Framework, and then continue installing Data Archive.

2. To advance to the Feature Selection window, select Next .

3. In the Feature Selection window, select the PI Data Archive check box to install it on your computer.

   

   The directory paths for Data Archive and other PI component installation files are shown.

4. Click the Individual Features tab to view specific subsystems and components that are also part of your installation.

   Note: By default, the setup kit configures all the required Data Archive services to run with virtual service accounts. In addition, the setup kit ensures these virtual service accounts have proper access to key folder paths as part of the install process.

   For upgrades, the setup kit checks for any existing user-configured accounts associated with Data Archive services and preserves these configurations during the upgrade process. After the upgrade, if PI Archive Subsystem and PI Snapshot Subsystem are not set to run with virtual service accounts, you must configure these two services to run with the same user. Regardless of the configuration, you must ensure that accounts for all Data Archive services have permission to access key folder paths, such as those for backup and archives. This is especially true if changes are made after the installation or upgrade.

5. Click Next to continue with the installation.

   The Data Archive window appears.

6. Specify a license file (pilicense.dat) for your installation in the License Directory field.

   For more information, see Understand licensing a new Data Archive deployment.

7. Optional. Change the default directory paths for Data Archive in the Data Directories fields. Refer to your Installation Worksheet that you filled out in Phase 1: Pre-installation for this information.

   • Historical Archives: Directory path where historical (non-future) archive files will be created. The default is the drive with the most free space.

   • Future Archives: Directory path where future archive files will be automatically created when data is received. You can modify this location after installation through PI SMT. The initial size starts at 1MB and grows dynamically. Each future archive file covers one calendar month.

   • Event Queues: Directory path where event queues will be created. By default, this is the drive with the second most free space (as long as that drive has at least 5 GB of free space).

8. Accept the archive setting values for Data Archive, or enter new values in the Archive Settings fields.

   • Size in MB for historical archives: The default archive size is approximately 1/3 of the physical memory size on your computer, up to a maximum of 10,240 MB. The size may be limited by your point count limit of your license file.

   • Max point count for historical archives: The maximum point count is the archive size in MB multiplied by 512.

   • Automatic creation for historical archives: Specify whether to disable or enable automatic creation for historical archives. The default is set to Enabled.

9. Click Next to advance to the Certificates Selection page.

10. Take one of the following actions:

    • To enable TLS certificates encryption for OpenID Connect (OIDC), ensure that the Configure certificate for TLS Encryption option is selected.

    Note: If you installed and configured the AVEVA Identity Manager using the PCS for the PI System setup kit and opted to use the PCS-generated certificate, the PCS certificate’s SSL Certificate thumbprint will be selected automatically after selecting Configure certificate for TLS Encryption. This certificate applies to any PI Server services selected for installation. This selection configures automatic certificate rotation for PI Server services.

    • If you do not plan to use TLS, deselect the Configure certificate for TLS Encryption option and proceed to step 13.

    See, Certificate management for Data Archive.

    

11. Click Select to choose a new certificate.

    The Select Certificate dialog opens. Any certificate that is already installed and meets certificate requirements will be detected and displayed.

12. Select OK.

    The SSL Certificate thumbprint is displayed in the TLS Certificate section. The TLS certificate thumbprint is required for encryption. To later change or set the thumbprint of the certificate that Data Archive presents to clients, see Data Archive.

13. Select Next.

    The PI to Data Hub Agent page opens.

14. Take one of the following actions:

    • To install the PI to CONNECT Agent, confirm that the Download and install this version option is selected, then select Next. See Set up PI to CONNECT Agent for more information on setting up the agent.

    • If you do not plan to install the PI to CONNECT Agent, select the Do not download and install option, then go to step 18.

    If all checks pass, the PI to Data Hub Rules page is bypassed and then the Service Accounts page opens.

15. Optional. To change the service account, select the Accounts Name down arrow, then select <Browse>.

    The Select User or Service Account dialog opens.

16. Optional: Make and save your changes, then return to the Service Accounts page.

17. Click Next to continue to the Summary page, then select Install to begin installing all selected components.

    The Installation Progress window opens, then the Complete window opens when all components have been installed.

18. If you did not enable TLS certificates or include the PI to CONNECT Agent as part of your installation, click Close to exit the setup.

19. Optional. If you enabled TLS certificates for OIDC, take one of the following actions:

    • To register Data Archive with the AVEVA Identity Manager, ensure that the Run the OpenID Connect Authentication after setup exits option is selected.

    • To bypass the OpenID Connect Configurator utility, deselect the Run the OpenID Connect Authentication after setup exits option.

20. Optional. If you installed the PI to CONNECT Agent, take one of the following actions:

    • To set up a connection to AVEVA PI to CONNECT after installation, ensure that the Run the PI to Data Hub utility after setup exits option is selected.

    • To bypass PI to CONNECT utility, deselect the Run the PI to Data Hub utility after setup exits option.

21. Restart Data Archive.

Next, Register PI Server components with the AVEVA Identity Manager if you selected the "Configure certificate for TLS Encryption" option and want to use OIDC for claims-based authentication.

See Set up PI to CONNECT Agent for instructions on configuring the agent before data transfer to the AVEVA Data Hub cloud portal.