PI security configuration for PC Client, Windows Services, and Web Services

PI Manual Logger PC Client, PI Manual Logger Windows Services, and PI Manual Logger Web Services use the PI SDK to communicate with PI Data Archives. All users require read access to the PI Data Archive. Users who send tour run data to PI Data Archive require read access to the point security and write access to the data security for the relevant tags. A PI mapping (or a PI trust connection) is therefore required. Before you start loading points to PI Manual Logger, configure the server connection to use a PI mapping (or a PI trust login).

PI mapping

For PI Data Archive version 3.4.380 or later and PI SDK 1.3.8.388 or later, OSIsoft recommends using Windows security through PI mappings. Windows security provides the strongest authentication and full Windows account traceability in the PI Data Archive log and audit trail records.

For details on how to configure PI mapping, refer to the PI Data Archive 3.4.390 Security Configuration Guide. You can obtain this manual from the Downloads tab at OSIsoft Customer Portal.

PI trust

To configure a PI trust, refer to the Manage Trusts section of the PI System Management Tools (PI SMT) User Manual/Help, which you can obtain from the Downloads tab at OSIsoft Customer Portal.

For PI trusts, the Application Name is:

• PimlWindows.exe for PI Manual Logger PC Client

• PimlWindowsServices.exe for PI Manual Logger Windows Services

• w3wp.exe (IIS 6+) or aspnet_wp.exe (IIS 5) for PI Manual Logger Web Services