Connecting to AVEVA Insight

To use the Historian SDK with AVEVA Insight, use the connection string that you've created 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.

Use HistorianConnectionArgs and the rest of the SDK as you would with on-premises Historian.

Required Components

To use the Historian SDK with AVEVA Insight, place a copy 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.

Scope

For security reasons, the scope of all 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 tagname and FQN property. All SDK access is based solely on the tagname.

SDK Limitations

None of the retrieval-related methods for events or time-series data are supported when using it against AVEVA Insight. Use the REST interface for retrieval instead.

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 REST/OData (“iHistory”) 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 sign-ins. The REST interface supports: 

• Basic authentication
  Basic authentication is supported by more applications and is often simpler to use. 
• Bearer token (OAuth) authentication
  Unlike the tokens described above which are associated with a data source, “bearer tokens” have an expiration and are always associated with a specific user account.

For more information about building AVEVA Insight solutions with the REST/OData (“iHistory”) interface, see AVEVA Insight Help for Solution Builders.