AVEVA CDS

AVEVA Connect Data Services: formerly ADH, and before that OCS.

Coming soon

The connection form is here and an endpoint can be saved, but no task can write
to it yet. Stream builds a writer for file, Microsoft SQL Server, Oracle,
Databricks and Snowflake destinations today; CDS is not among them.

A task pointed at a CDS endpoint says so on its Output tab rather than failing at
run time. Configure one now if you want the connection ready; do not schedule work
against it.

Fields

Stream authenticates as a registered application, not as a person, so the form
asks for a tenant, a client ID and a client secret rather than a username and
password. Create that application in AVEVA Connect first: Stream cannot register
one for you.

Field	Notes
Resource	The regional endpoint: prefilled with the US-West default
Namespace Id	The namespace inside that region
Tenant Id	The CDS tenant
Client Id	The registered application
Client Secret	Its secret: stored encrypted, never sent back to the browser

Resource is regional, and it matters

A namespace in one region is not reachable through another region's resource.
If a namespace you can see in the CDS portal is reported as missing, the resource
is the first thing to check, before the namespace ID and before the credentials.

Related

• Endpoints: the list, and how a connection is tested
• Cognite CDF: the other industrial cloud type