Service Configuration

On the Services page, use settings in the Service Configuration pane to select and configure installed services.

• Service name

  The Service name field shows the name of the current interface service. This service name is obtained from the interface executable.

• ID

  The service ID field is enabled only if the interface service has not yet been created, and can be used to select a new service ID for the selected interface. Changing the service ID causes the PI ICU to rename the interface and to reload all interfaces. If a service ID is selected that is already in use, the text box background turns yellow, and the service ID save button is disabled. The service ID is usually a number, but can be any text up to 20 characters in length.

• Save

  The save button is enabled once a new valid service ID has been selected for an interface whose service has not yet been created. Changing the service ID causes the PI ICU to rename the interface and reload all interfaces.

• Display name

  The Display name text box shows the current display name of the interface service. If there is currently no service for the selected interface, the default display name is the service name with a 'PI-' prefix. Users may specify a different display name, although it is recommended to append the prefix 'PI-' to the name of the interface to indicate that the service is part of your PI system.

• Log on as

  There are two choices for the Log on as account. The default depends on the OS your system runs and the version of UniInt that the interface uses.

  If you are logging on to install an interface, an account with administrator-level privileges must be used.

  Note: Currently, ICU always runs with elevated (admin) permissions.

  For optimal security, run the interface service under an account with the least required privileges, and limit the rights of the identity to access resources. Preferably, use a local non-system or service account.

  • Several account types are available:

    • Domain User Account

      If the service must interact with network services, access domain resources like file shares or if it uses linked server connections to other computers, then consider using a minimally-privileged domain account. This account should be pre-created by domain administration in your environment.

    • Local User Account

      If the computer is not part of a domain, a local user account without Windows administrator permissions is recommended.

    • Local System

      This is a very high-privileged built-in account. It has extensive privileges on the local system and acts as the computer on the network. The actual name of the account is NT AUTHORITY\LOCALSYSTEM.

    • Network Service

      This is a built-in account that has more access to resources and objects than members of the Users group. Services that run as the Network Service account access network resources by using the credentials of the computer account. The actual name of the account is NT AUTHORITY\NETWORKSERVICE.

    • Virtual - Service Account

      This is a built-in account introduced with Windows Server 2008 R2 and Windows 7. It requires no password management and has the ability to access the network with a computer identity in a domain environment. The actual name of the account is NT SERVICE\servicename.

    • UserName

      If you select [Domain\]UserName for Log on as, then the Username, Password, and Confirm Password text boxes appear. Enter the user name that you want the service to use. This must be a valid Windows/domain account.

    • Password / Confirm password

      If you select [Domain\]UserName for Log on as and the specified user name requires a password, then enter the password in this field. If no password is required, this field can remain blank. The Confirm password text box is used to confirm the password typed into the Password field.

    • OMF health configuration

      Available only with interfaces that support OMF Health Tags and after creating a service. Once selected, a configuration file is created and the user specifies the OCS and/or PI Web API endpoint(s). For further information on OMF Health Tags, refer to the PI Universal Interface (UniInt) Framework user guide.