The 64-bit PI-API is delivered by a Windows Installer package that prompts for installation directory and allows configuraton of optional features. The default is to install all features. The PI-API MSI may be installed by itself, but it is recommended that the full setup package be installed. This setup wrapper package installs the PI SDK 64-bit (PISDK64) for use by the PIPC log file service (pilogsrv) and the PI buffer subsystem (pibufss) for use in buffering. pilogsrv is dependent on the PISDK64 for log file consolidation into the PINS message log. If the PISDK64 is excluded, then PI-API messages will not be added to the local PINS log, but the log file size will be managed by the PIPC log file service. If the PI buffer subsystem is excluded, the PI-API buffer service may be configured for buffering if desired.
The 32 and 64-bit PI-API libraries may be independently installed. There is no dependency on configuration or other files from other setup kits in the 64-bit PI-API setup kit.
For new installations, a root path for the PI-API files is requested and is called the PIHOME directory. For upgrades, the existing installation path is detected and used. If a new installation directory is desired, the PI-API and all 64-bit programs that are installed in the PIHOME directory must first be uninstalled, and then installed in the new location. If configuration from the previous installation is to be preserved, make a backup copy of the piclient.ini file and any adjustments to the site start and stop files.
During installation, the PATH environment variable is appended with the PIHOME\bin directory in order for PIAPI programs to locate the piapi.dll library. For programming purposes, the PIHOME64 enviroment variable is created so that Visual Studio projects may reference it to locate include and library paths.
Typically, the following programs and files are installed under the PIHOME directory.
The bufserv program is installed as a service to start manually. If installed as an upgrade, the previous setting is retained. The pilogsrv service is installed to start automatically and the mode to migrate pipc.log files to the PINS log is enabled by default.
The piapi.chm help file source is the same for both the 32 and 64-bit PI-API. Therefore, the latest installed kit will deliver the most current documentation.
There is a chance that programs may access a version of the PI-API that is different from the one just installed. This situation occurs when an old copy of the piapi.dll file exists in a directory specified in the PATH environment variable, the current directory, or paths entered in the registry. If the piapi.dll version that a program is using is not the version just installed, ensure that all previous copies of piapi.dll are found and renamed. A system internals utility named listdlls.exe may be helpful in determining the path and version of the piapi.dll that is in use by a running program.
Because PI API 2016 for Windows Integrated Security uses the PInet3 protocol, the pinetmgr and pimsgss services must be installed and running for the API-based applications to connect to the PI Data Archive. To ensure that the services are available, the setup kit bundle includes the PI Network Subsystems (PINS) install package.
The files in the include and library directories are NOT included in the PI API 2016 for Windows Integrated Security installation. The PI API should not be used for new application development, which is why the development files are not included. Applications developed for the old versions of the PI API will run with PI API 2016, the older include and libraries files can be used with PIAPI 2016.
For new developement projects, OSIsoft provides a number of alternatives for accessing the PI system. Please refer to the Developer Technologies section of the OSIsoft Technical Support website for more information.