3.16.3.3. AVEVA CONNECT
From the Edit Historian Connection window you can select AVEVA CONNECT for reading and/or writing data. The DataHub instance uses HTTPS to communicate with AVEVA CONNECT. It uses OAuth2 client credentials for authentication, SDS REST APIs for reading historical data, and OMF ingress for writing data.
Connection Settings
- Label
A unique text string used to identify this connection, including for when configuring store and forward, and to create the database name or retention policy in some historians. The label can contain only letters, numbers and the underscore (
_) character.- Tenant Id
The AVEVA CONNECT Tenant ID used for this connection.
- Namespace Id
The Namespace ID within the AVEVA CONNECT tenant. Streams and OMF data are read from and written to this namespace.
- Client Id
The OAuth2 Client ID used to authenticate this connection.
- Client Secret
The OAuth2 Client Secret associated with the Client Id.
- Resource URL
The base resource URL for the AVEVA CONNECT tenant. For example:
https://uswe.datahub.connect.aveva.com.- Max points read per message
The maximum number of values that will be read in a single transaction. Setting this value to zero uses the built-in default. If necessary, the DataHub instance will use multiple read transactions to fully retrieve data over a period.
- Read timeout (seconds)
The number of seconds to wait for a read request before timing out. This setting is used when reading historical data from AVEVA CONNECT.
- Max read retries
The maximum number of times the DataHub instance will retry a failed read request. Retries are used for transient errors, such as temporary network failures or service throttling.
- Initial retry backoff (ms)
The initial number of milliseconds to wait before retrying a failed read request.
- Max retry backoff (ms)
The maximum number of milliseconds to wait between retry attempts.
- Accumulation time (ms)
The number of milliseconds that the DataHub instance will buffer data in memory before sending it to Kinesis. Setting this value to zero means that no accumulation time will be enforced.
If both this value and Maximum # of buffered values (below) are specified, then the DataHub instance will write all buffered values to CONNECT whenever the first of these two limits is reached.
- Maximum # of buffered values
The maximum number of values that the DataHub instance will buffer in memory before transmitting them to CONNECT. Setting this value to zero means that all values will be sent as soon as possible.
- Read-only - do not write to database
Prevents the DataHub instance from writing to AVEVA CONNECT.
- Log writes at information level
Checking this option causes messages regarding successful writes to the database to be logged at the level in the DataHub Event Log. If this is not checked then these messages are logged at the level and are therefore normally hidden from the user.
Modify Point Names, Data Sampling and Forwarding
Please see Modify Point Names, Data Sampling or Forwarding in Connection Configuration for how to configure these options.
Once you have completed the Amazon Kinesis-specific configuration, you can return to Picking Points in General Options to continue.