Define a Replication Server

If you want to connect from AVEVA Historian to AVEVA Insight as a tier-2 server, follow these steps.

To add a replication server

1. Start the System Management Console (sometimes labeled "System Platform Management Console").

2. In the left pane, expand a server group and then expand a server.

3. Expand Configuration Editor, expand System Configuration, and then expand Replication.

4. Right-click Replication Servers and select New Replication Server. The New Replication Server dialog box appears.

   

5. Specify a Node Name and Description for the tier-2 server. The description you provide appears in the System Management Console and in Historian Client reports.

   Note: In the case of using AVEVA Insight, you are just providing a label in Node Name. It is not reused elsewhere. Do not type an IP address.

6. Check the Replication to AVEVA Insight check box.

   

7. Select Register.

   This launches the AVEVA Insight Publisher data source registration wizard.

8. Select Publish.

9. On the Region page, select the region where the majority of your users work.

10. If your internet access requires a proxy, on the Web Proxy Configuration page, specify a URL and port. For example:

    

    By default, Publisher displays user-level the proxy settings associated with your account. Change these as needed to service-level settings so data can be sent to AVEVA Insight.

    Note If you are using a version of AVEVA Historian between version 2014 R2 SP1 Patch 02 and version 2017 Update 3, you will not see this page. Instead, you will create and use a config file to set the proxy.

11. Select Continue.

12. If prompted, sign in to AVEVA Insight Publisher.

    Note: You use your same login credentials (email address and password) for AVEVA Insight, Publisher, and AVEVA Insight mobile app.

13. Type a name for your application. This will be the name of the data source in AVEVA Insight.

14. Follow the on-screen instructions to finish creating the data source in AVEVA Insight and start publishing your data.

15. Once the registration process is complete, you'll see encrypted information in the Connection Info box.

    Here's an example of the encrypted information you'll see:

    

    Important: Do NOT tamper with this encrypted string in any way.
    
    Also, this information is valid only on the computer that created it. If you backup or restore Runtime, or use the DB Config Import/Export utility to move it to a different computer, you must re-register using the same data source name and then select the Replace option.

16. Select Next. The New Replication Server - Advanced dialog box appears.

    

    You can use the default summary and simple replication tag naming schemes, or you can create your own.

17. In the Summary Replication Tag Naming Scheme and Simple Replication Tag Naming Scheme areas, select the replication tag naming scheme to use. Specify a custom naming scheme by selecting Custom and selecting the ellipsis button to the right of the box. The Naming Scheme dialog box appears. For information about configuring the naming scheme, see Specifying Naming Schemes for Replication.

18. Configure the remaining advanced settings as follows:

    • Min SF Duration
      Enter the minimum duration in seconds for the replication service to function in store-and-forward mode. The replication service functions in store-and-forward mode for this length of time even if the condition that caused the replication service to function in store-and-forward mode no longer exists. The duration can be an integer from 0 to 3600. Pick a value that provides a smooth transition for store-and-forward operation and prevents the system from repeatedly going in and out of store-and-forward mode.

    • Compression Enabled
      Check this box to enable compression for the packets sent to the replication server. For guidelines on using compression, see the performance information in the System Platform Installation Guide.

    • Buffer Count
      Enter the number of 64KB buffers to allocate for the new replication server. This can be an integer from 128 to 2048. You may need to increase the buffer count to accommodate high data rates.

    • Bandwidth

      • Check Unlimited for unlimited bandwidth to be used by the HCAL to communicate with the historian.

      • Leave it unchecked and enter a value in the Kbps box to specify a custom bandwidth. This can be an integer from 10 to 1000000.

        Setting a limit on the bandwidth throttles the amount of data that is sent during operations such as a store-and-forward, an update, or a CSV export. You commonly use this feature when you have a WAN with a low bandwidth. For example, suppose your WAN has a 128kbps bandwidth between the tier-1 and tier-2 historians. If you have real-time streaming data that requires 64kbps for normal operation but the network is down for 8 hours and information is saved for store-and-forward, it will take 8 hours for the data to be uploaded. If you leave this set to Unlimited, it will work fine.

        But if you have 256kbps bandwidth that you have to share with other applications, set this to 128kbps to throttle the store-and-forward data and anything that isn’t streaming. This prevents the historian’s operations from choking the other applications for bandwidth. The most common symptom of a problem is that when you come out of store-and-forward and start sending data, the remote desktop is very sluggish and unresponsive. The bandwidth limit also applies to streaming data. However, streaming data will not be throttled, and instead HCAL will be put into store-and-forward mode. For example, if the streaming bandwidth is always 96kbps, and you set the limit at 128kbps, there will be 32kbps remaining for store-and-forward to use. However, if you had a sudden spike and streaming jumped up to 156kbps, it would exceed the limit and force HCAL into store-and-forward mode.

19. Select Finish. The new replication server appears in the replication server list.