Prepare egress destinations

CONNECT data services and PI Server destinations may require additional configuration to receive Open Message Format (OMF) messages.

CONNECT data services

To prepare CONNECT data services to receive OMF messages from the adapter, create an OMF connection in CONNECT data services. Creating an OMF connection results in an available OMF endpoint that can be used by the adapter egress mechanism.

Complete the following steps:

1. Create a Client.

   The Client Id and Client Secret will be used for the corresponding properties in the egress configuration.

2. Create an OMF type Connection.

   The connection should link the created client to an existing namespace where the data will be stored.

   The OMF Endpoint URL for the connection will be used as the egress configuration Endpoint property.

AVEVA PI Server

To prepare a AVEVA PI Server to receive OMF messages from the adapter, a PI Web API OMF endpoint must be available.

Complete the following steps:

3. Install PI Web API and enable the Open Message Format (OMF) Services feature.

   • During configuration, choose an AF database and PI Data Archive where metadata and data will be stored.

   • The account used in an egress configuration needs permissions to create AF elements, element templates, and PI points.

4. Configure PI Web API to use Basic and/or Kerberos authentication.

For complete steps, as well as best practices and recommendations, see the following topic in the PI Web API User Guide: Authentication methods.

Note: The certificate used by PI Web API must be trusted by the device running the adapter, otherwise the egress configuration ValidateEndpointCertificate property needs to be set to false (this can be the case with a self-signed certificate but should only be used for testing purposes). To continue to send OMF egress messages to the PI Web API endpoint after upgrading PI Web API, restart the adapter service.