Health endpoints parameters
- Last UpdatedOct 27, 2025
- 1 minute read
- PI System
- Adapter for OPC UA 1.6
- Adapters
The following parameters are available for configuring Health endpoints:
|
Parameter |
Required |
Type |
Description |
|---|---|---|---|
|
id |
Optional |
string |
Uniquely identifies the endpoint. This can be any alphanumeric string. If left blank, a unique value is generated automatically. Allowed value: any string identifier |
|
endpoint |
Required |
string |
The URL of the OMF endpoint to receive this health data. Allowed value: well-formed http or https endpoint string |
|
username |
Required for PI Web API endpoints |
string |
The username used to authenticate with a PI Web API OMF endpoint. AVEVA PI Server: Allowed value: any string |
|
password |
Required for PI Web API endpoints |
string |
The password used to authenticate with a PI Web API OMF endpoint. AVEVA PI Server: Allowed value: any string |
|
clientId |
Required for CONNECT data services endpoints |
string |
The client ID used for authentication with a CONNECT data services OMF endpoint. Allowed value: <any string> |
|
clientSecret |
Required for CONNECT data services endpoints |
string |
The client secret used for authentication with a CONNECT data services OMF endpoint. Allowed value: <any string> |
|
tokenEndpoint |
Optional for CONNECT data services endpoints |
string |
Retrieves a CONNECT data services token from an alternative endpoint. Allowed value: well-formed http or https endpoint string |
|
validateEndpointCertificate |
Optional |
boolean |
Disables verification of destination security certificate. Use for testing only with self-signed certificates; AVEVA recommends keeping this set to the default (true) in production environments. Allowed value: true or false |