Create a Server-to-Server Collector

Before you begin

  1. Deploy Proficy Historian for AWS.
  2. Install collectors. You can install them on-premises or on a VPC (which can be different from the one on which Proficy Historian for AWS is deployed).

About this task

Using the Server-to-Server collector, you can only send data from an on-premises Historian server to the Historian server deployed on cloud; however, you cannot send data if both the servers are on cloud.
Features:
  • You can browse the source for tags and their attributes.
  • Only unsolicited data collection is supported.
  • The supported timestamp resolution is 100 milliseconds.
  • Data compression is supported.
  • Floating point, integer, and string data are supported.
  • Device timestamps are accepted.

When a time-based or an event-based trigger of a destination tag occurs:

  1. The calculation formula for the destination tag is executed.

    This typically involves fetching data from one or more tags on the source server.

  2. A raw sample or calculation error is determined.

    You can use conditional logic in your calculation formula to determine if a sample should be sent to the destination.

  3. The raw sample is delivered to the destination server, utilizing store and forward when necessary.
  • When a tag is added by browsing, only certain tag properties are copied from the source tag to the destination tag. Consider what properties are necessary for your application and configure them manually. For information on which properties are copied, refer to Tag Properties that are Copied.
  • If you change a tag property on the source tag (EGU Limits, descriptions, and so on), the property does not automatically change on the destination tag. You can manually change the properties of a destination tag.

Best Practices

  • We recommend that you install the Server-to-Server collector on the source Historian machine. When you do so, the collector can preserve the collected data (store and forward) even if the collector and the destination server become disconnected.
  • Collection on a tag-by-tag basis is preferred, according to scheduled poll times or upon data changes. One sample is collected for each trigger.
  • The Server-to-Server collector can perform calculations on multiple input tags as long as the input tags are on the same source Historian.
  • Use polled triggers to perform scheduled data transformations like daily or hourly averages. Use unsolicited triggers to replicate data in real time, as it changes.
  • Use event-based triggers to replicate data throughout the day. The samples can be held incoming and outgoing store and forward buffer when necessary. You cannot schedule batch replication of raw samples. For example, you cannot, at the end of the day, send all raw samples for tags to the destination.
  • All input source tags for the calculations must originate from the source archiver. For instance, you cannot directly add a tag from server1 plus a tag from server2 and place the result on server2. You can, however, collect tags from server1 to server2, and then use the Server-to-Server collector to accomplish this. This requires two Server-to-Server collector instances, one running on each machine.

Procedure

  1. Run Command Prompt as an administrator.
  2. Run the CloudHistorianConfigurationUtility.exe file. It is provided along with the collectors installer. After you install collectors, it will be available in the C:\Program Files\GE Digital\Historian Cloud Config folder by default.
  3. Enter the number corresponding to creating a collector instance.
  4. Enter the following details:
    Field Description
    NLB DNS

    Enter the Amazon Network Load Balancer (NLB) DNS.

    Tip: To find the NLB DNS:
    1. Access the EKS cluster on which you have deployed Proficy Historian for AWS.
    2. Access the EC2 instance.
    3. In the navigation pane, under Load Balancing, select Load Balancers.
    4. Select the load balancer for which you want to find the DNS.
    5. In the Description section, copy the DNS name.
    Username Enter the username to connect to Proficy Historian for AWS.
    Password Enter the password to connect to Proficy Historian for AWS.
    Tip: This is the value you entered in the Password field under UAA Configuration when you created the stack.
    A list of collector types appears.
  5. Enter the number corresponding to the collector that you want to create.
  6. Enter the following details:
    Field Description
    Interface name Enter a unique interface name for the collector.
    Source Historian server Enter the host name or IP address of the source machine on which the Historian server is installed.
    The Server-to-Server collector is created and started.