Understand mapping for multiple interfaces on the Interface node

This deployment scenario considers an Interface node with multiple interfaces, where the interfaces do not use the same PI identity to connect to Data Archive. In this type of scenario, a different user account must be created for each interface and then mapped to the appropriate PI identity. You will need to start by creating a new Windows domain accounts for each PI identity.

1. Create a Windows domain account for each of the PI identities you plan to use.

2. Map a new account to a distinct PI identity used on the Interface node. Repeat until all of the distinct PI identities have been mapped.

Mapping three PI interfaces and two PI identities

Consider a deployment with three interfaces running on the Interface node: Interface1, Interface2 and Interface3. In this scenario, Interface1 and Interface2 connect with the same PI Identity: Identity12, as determined in Step 2. Interface3 connects a different PI Identity: Identity3). All three interfaces run through a Local System account, and the Interface node and PI Data Archive are on the same domain.

Mapping the interface node to Identity12 grants the appropriate permissions for Interface1 and Interface2. However, for Interface3 to continue using Identity3, a new mapping is necessary. A Windows account can only be mapped to one identity, therefore it is necessary to identify (or create) a new Window account for Interface3.

Create a new Windows domain user User3. Then, create a new PI mapping that associates the new User3 account to Identity3.