Data endpoints examples

The following are examples of valid data endpoints configurations:

Egress data to CONNECT data services

[

{

"id": "CONNECT data services",

"endpoint": "https://<CONNECT data services OMF endpoint>",

"clientId": "<clientid>",

"clientSecret": "<clientsecret>"

}

]

Egress data to Edge Data Store

[

{

"id": "Edge Data Store",

"endpoint": "http://localhost:5590/api/v1/tenants/default/namespaces/default/omf"

}

]

Note: In order to send data from an adapter to an Edge Data Store instance, both products must be installed on the same device. This includes module-to-module scenarios.

Egress data to PI Web API

[

{

"id": "PI Web API",

"endpoint": "https://<pi web api server>:<port>/piwebapi/omf/",

"userName": "<username>",

"password": "yourPassword"

}

]

Egress data to PI Web API using a valid secret Id

See How to reference secrets for more information on how to use a secret Id.

[

{

"id": "PWA_OIDC",

"endpoint": "https://zrpiserver/piwebapi/omf",

"userName": null,

"password": null,

"clientId": "oidc-client",

"clientSecret": "{{System.HealthEndpoints.PWA_OIDC.ClientSecret}}",

"debugExpiration": null,

"tokenEndpoint": "https://zrpiserver/identitymanager/connect/token",

"validateEndpointCertificate": false

{

]

Egress data to PI Web API using negotiate

See How to reference secrets for more information on how to use a secret Id.

[

{

"id": "PI Web API",

"endpoint": "https://<pi web api server>:<port>/piwebapi/omf/"

}

]

Note: Egressing data to PI Web API using negotiate only works if your adapter is installed on a Windows OS.