The 32-bit PI-API library may be used to create programs to run under the Microsoft Windows 32-bit operating systems. The 32-bit library is also compatible with the WOW64 layer on Windows 64-bit operating systems. The 64-bit library supports only Windows 64-bit (x64) operating systems beginning with Windows 2003. Windows 9X support ended with PI-API version 1.6.1
The current version of the 32-bit PI-API is installed as part of the 32-bit PI-SDK. That is, you must run the 32-bit PI-SDK installation program in order to install the 32-bit PI-API. The installation path is defined during initial install and subsequent upgrades cannot change the path. A full uninstall must be performed to change the installation path. The default installation path, referred to as PIHOME, is Program Files\PIPC. On 64-bit operating systems, this is redirected to Program Files (x86)\PIPC.
Typically, the following programs and files are installed under the PIHOME directory.
The bufserv program is installed as a service as manual or automatic start depending on the choice during install. 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.
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 piapi32.dll file exists in a directory specified in
the PATH environment variable, the current directory, or paths entered in the
registry. If the piapi32.dll version that a program is using is not
the version just installed, ensure that all previous copies of
piapi32.dll are found and renamed. The Windows File Manager Search
command (under the File menu) can also be used for this purpose. This may also
be done from a command shell using the
dir command with the
/s option starting at the root of each disk. For example:
dir /s piapi32.dll
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, library and example 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.