Connect a Historian SDK app to your product

If you've created an application with the AVEVA Historian SDK, you can use that application to connect with AVEVA Insight.

To connect your Historian SDK application with AVEVA Insight

1. Use Historian Publisher to register your application.

2. Use the connection token from Historian Publisher in the constructor for HistorianConnectionArgs:

   HistorianConnectionArgs connectionArgs = new HistorianConnectionArgs(connectionString);

   The connection string eliminates the need to set the other server-related properties, such as:

   • ServerName

   • TcpPort

   • UserName

   • Password

   • UseArchestrAUser

   • IntegratedSecurity

     You must still set StoreForwardPath to a valid pathname.

3. Place copies of these components in the same directory as your SDK application:

   • aahStorage.exe

   • aahClientManaged.dll

   • ArchestrA.CloudHistorian.Contract.dll

   • Historian.CBE.dll

   • Historian.DPAPI.dll

     Note: Only the first two components are required for connecting to on-premises AVEVA Historian.

Access limitations

For security reasons, access to AVEVA Insight is limited to the data source associated with the connection string. It has no access to tags registered for other data sources. SDK-based connections do not have an associated user context and so do not apply any tag-level security.
In the AVEVA Insight environment, every tag has a fully-qualified name (FQN), which includes a data source name plus a tag name (for example, Weather.MaxTemp). All SDK access is based solely on the tag name.

Using REST retrieval

Once you have all of the above and have started sending data to the AVEVA Insight system, you can retrieve it using the OData/JSON interface. This interface uses a simple HTTP GET method where the query is specified in the URL.

Unlike the SDK-based access, REST-based access requires user-based logins. For more information, see the Data retrieval section for the Historian Data REST API.