AVEVA Historian Server connection configuration

To use the AVEVA Historian Client applications, you must first connect to an AVEVA Historian using a valid user account that has the right to retrieve data.

You can either use your Windows user account (integrated security) or a valid SQL Server user account or a managed Historian account, depending on how the AVEVA Historian is configured.

Historian Client Trend supports connectivity to Managed Historian, running on Microsoft Azure. Managed Historian is an OData feed which can be accessed using Managed Accounts. The Managed Account credentials come with your AVEVA Cloud subscription and allow you to connect from Historian Client Trend using the OData feed option to the Managed Historian.

Ask your administrator what type of user account you must use to access the server. Server connections are shared among the AVEVA Historian Client applications. For example, once you have configured a server connection in the Trend application, you can use it in the Query application as well.

Note: Managed Historian connection and retrieval is only available for the Trend Client. The Managed Historian server registration will be visible in other Historian Client tools, but is not supported and should not be used.

When you start an AVEVA Historian Client application, you are not automatically logged on to every server that you configured before. You are only logged on to a server when you do the following:

• Open a file that causes data to be retrieved for a tag on that server.

• Expand a server in the Tag Picker to view its Tag List.

• Manually log on to the server.

  Note: Make sure you always log on to the server manually in case you are using a Managed Historian connection.