The ADH-Driver provides communication between IOTA Vue the Cluster (back-end) and AVEVA Data Hub (ADH) (source).
The AVEVA Data Hub (CONNECT data services) provides scalable, secure industrial data management service that makes it easy to aggregate, contextualize and securely share real-time data within or outside the company's network.
The ADH driver supports the following object types:
| IOTA Type | Supported? | Source Type |
|---|---|---|
| Tag | 🟢 | Stream |
| Asset | 🟢 | Asset with Metadata and StreamReferences |
| Timeframe | 🟢 | Event with Metadata and StreamReferences |
The driver is state-less, i.e. driver does not maintain source connections and any data caches.
Single ADH-Driver service can support multiple connections to different AVEVA Data Hub tenants.
The driver uses two architectural styles to communicate with ADH: REST and GraphQL.
QuickStart
The driver setup process requires 3 steps:
Configure IOTA Vue data source for communication with the ADH-Driver service.
Install ADH-Driver service on windows PC where both IOTA Vue and AVEVA Data Hub can be accessed via the network.
Configure AVEVA Data Hub connections
Diagram
Technical Specification
| Description | Value |
|---|---|
| Development Language | C# |
| Processor Architecture | 64-bit |
| Supported Operating Systems | Windows 2012+ |
| Minimum Requirements CPU/Memory | 4 cores / 8 Gb |
| Deployment Size | 13.7 Mb |
| Data modes | Read |
| Request/Response pattern | Asynchronous |
| Source Communication | REST, GraphQL |
| Back-end Communication | NATs message bus |
| Message bus driver type | adh |
| Near Real-Time Data Updates | Yes |
| Multiple PI Systems/Data Archives | Yes |
Dependencies
| Name | Version |
|---|---|
| Microsoft Windows | 2012 and above |
| Microsoft .Net Framework | 4.7.2 |
Security
Source Security
THE ADH-Driver uses client-credentials approach for server-to-server communication that does not require user interaction.
The driver authenticates with the AVEVA Data Hub endpoint using Client ID and Client Secret.
A Client Id and Client Secret are used to authenticate and retrieve a token that provides access as a headless client.
IOTA API (back-end) Security
The ADH-Driver uses NATS message bus to communicate with back-end IOTA API. The two-way data traffic is encrypted using Transport Layer Security (TLS) on port 443.
In addition, the message bus communication security model uses public-key signature system based on Ed25519 called NKeys.
With NKeys, the server can verify identities without ever storing or ever seeing private keys.
The authentication system works by requiring a connecting client to provide its public key and digitally sign a challenge with its private key.
The server generates a random challenge with every connection request, making it immune to playback attacks.
The generated signature is validated against the provided public key, thus proving the identity of the client.
If the public key is known to the server, authentication succeeds.