Overview of the Server-to-Server Distributor

Note: When instantiating Server-to-Server and Server-to-Distributor from Configuration Hub, the Historian Node Name is set to "historian-svc". Provide the NLB DNS in the Destination Historian server field during collector instantiation.
The Historian Server-to-Server distributor is used to send data from a smaller Historian server to a larger, centralized Historian server. You can then use this data for reporting and analytics.
You can use either the Server-to-Server collector or the Server-to-Server distributor to send data to a central Historian. However, using the Server-to-Server distributor has the following advantages:
  • It simplifies the process of configuring tags at the destination Historian.
  • It provides more flexibility at the SCADA level for tag configuration compared to the Server-to-Server collector.
  • It allows you to manage tags both from the source and destination Historian servers, whereas the Server-to-Server collector allows you to manage tags only from the destination Historian server.
You cannot, however, use the Server-to-Server distributor to send data to a cloud destination. Use the Server-to-Server collector for this purpose.
Features
  • You can browse the source for tags and their attributes.
  • Only the unsolicited data collection is supported; polled collection is not supported.
  • The supported timestamp resolution is 100 milliseconds.
  • The collector accepts device timestamps.
  • The collector supports data compression.
  • Floating point, integer, and string data are supported.

Limitations

  • The Server-to-Server distributor forwards only raw data samples, messages, and alarms. It does not perform any calculations on the data.