Learn about installation instructions
- Last UpdatedJan 24, 2025
- 2 minute read
- PI System
- Interfaces
AVEVA recommends that interfaces be installed on interface computers instead of directly on the Data Archive computer. An interface computer is any computer other than the Data Archive computer where the PI Application Programming Interface (PI API) is installed (see the PI API manual). With this approach, the Data Archive need not compete with interfaces for the machine's resources. The primary function of the Data Archive is to archive data and to service clients that request data.
After the interface has been installed and tested, buffering should be enabled on the interface computer. Buffering refers to either PI API Buffer Server (Bufserv) or the PI Buffer Subsystem (PIBufss).
In most cases, interfaces on interface computer should be installed as automatic services. Services keep running after the user logs off. Automatic services automatically restart when the computer is restarted, which is useful in the event of a power failure.
The guidelines are different if an interface is installed on the Data Archive computer. In this case, the typical procedure is to install the Data Archive as an automatic service and install the interface as an automatic service that depends on the PI Update Manager and PI Network Manager services.
Note: By default, buffering is not enabled on the Data Archive computer. Bufserv or PIBufss can be enabled on the Data Archive computer so that interfaces on the Data Archive computer do not need to be started and stopped in conjunction with the Data Archive.
Note: Catalog files are separate downloadable files, and are used for application allowlisting. If you use allowlisting, install the catalog files associated with your AVEVA products to ensure that those products function as intended. Windows catalog files that have been digitally signed by AVEVA can be used as a digital signature for 3rd party and other unsigned components installed by AVEVA setup kits. This facilitates a trusted way to verify these components and may be used for allowlisting purposes. For information on how to use catalog files for allowlisting, refer to the AVEVA Knowledge Base article: Allowlisting PI applications based on catalog files.
Related Links
- Learn about name conventions and requirements
- Learn about interface directories
- Learn about interface installation procedure
- Learn about PI trust for interface authentication
- Install interface as Windows service
- Learn about how to install interface service with PI Interface Configuration Utility (ICU)
- Learn about how to install interface service manually