Installation Notes 

This feature requires the software version 2018.1 or newer. We will refer to the servers and projects as Server1 (Project1) and Server2 (Project2). Go to Project1 > Dataset > DB > TagHistorian > Server IP column. This is where we will setup the column with the value of the method that is inside “Project2 > Script > Class > ClassName > MethodName”.

This column contains:

  • DataAccess: Hardcoded string to display that the content will be accessed directly
  • ServerIp: The Server2 IP address
  • CallbackMethodName: The name of the method that will be called to store data in Project2
  • BaseAddress: Information used by Project1 to check how to send local data to Server2
  • ErrorMessageReturn: Tag that will receive any error messages
  • Database format: [true – Normalized, false – Default Historian format]
  • CommunicationRows: Max number of rows that will transfer on each communication
  • DisableSynch: If true, force to cache locally, and the remote synchronization will not be executed


Explanation

The callback on Project2 will automatically receive the Historian data and save it wherever its configured, or it will do any other configured actions. The actions have to be manually coded using vb.net or c#. If the connection between these two servers is broken, the data will be automatically stored locally on Server1. Once the communication is back, they will synchronize the data as configured.

If the local file “.dbDataAccessHist” has been created on Server1, the built in feature will get the rows and send to the remote callback without scripts, using the current BaseAddress information.

  • No labels