Understand PI interfaces in Data Archive

PI interfaces are the software applications that take the data from your data source and send them to Data Archive. There are hundreds of different PI interfaces and each interface is fully documented in its own dedicated manual. However, most interfaces share a common set of features.

PI interfaces typically run on a dedicated system, called an interface node, which connects both to the data source and to Data Archive. The interface node might be a machine that is a part of the foreign data system, a stand-alone dedicated interface machine, or even a Data Archive server (PI to PI). Interface nodes can run multiple interfaces and connect to multiple Data Archive servers.

For most interfaces, it is important to configure buffering on the interface node. This prevents loss of data when Data Archive is not available, such as during an upgrade. Some interfaces (such as the UFL interface and batch interfaces such as the Emerson DeltaV Batch interface) do not require buffering because the data source itself is buffered. Consult the documentation for your interface.

Note: Interface nodes are sometimes referred to as API nodes or data source nodes.

Since data sources run without human intervention, user logins are not applicable. Before Data Archive 2016 R2, trusts were typically used to authenticate PI interfaces, while mappings were used for single sign-on for Windows users on Data Archive servers. With PI API 2016 for Windows Integrated Security, Windows authentication extends to PI interfaces.

Note: PI API 2016 for Windows Integrated Security extends Windows authentication to API-based client applications. If you choose to install PI API 2016 for Windows Integrated Security, you can use only Windows Integrated Security for authentication. Both trusts and explicit logins will fail.