Add AVEVA Insight as a replication server

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

Note: You must have an account with AVEVA Insight to complete these steps. If you do not have an AVEVA Insight account, go to the AVEVA Insight site (https://Insight.connect.AVEVA.com) and click Register.

To add AVEVA Insight as a replication server

1. In the Operations Control Management Console, expand a server group and then expand a server.

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

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

   

4. Select AVEVA Insight as the Replication Environment.

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

   Note: Although the field is called Node Name/IP Address, for AVEVA Insight this value is only used as a name, not as the connection target. The connection details are determined when you click the Register... button.

6. Click Register.

   This launches AVEVA Insight Publisher.

7. Follow the on-screen instructions to sign into AVEVA Insight, register your Insight data source, and publish your Historian replication tags to Insight.

   

   Note: For more information about publishing data to AVEVA Insight, see AVEVA Insight help (https://Insight.connect.AVEVA.com/help).

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

   Important: Do not tamper with this encrypted string in any way. 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.

   This is an example of the encrypted information you'll see:

   

9. Click 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.

10. 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 clicking the ellipsis button to the right of the box. The Naming Scheme dialog box appears. For information about configuring the naming scheme, see Specify naming schemes for replication.

11. 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.

    • 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.

    • SF free space

    • Compression Enabled

      Select this option to enable compression for the packets sent to the replication server. For guidelines on using compression, see the performance information in the AVEVA System Platform Installation Guide.

    • Bandwidth

      • Select Unlimited to allow unlimited bandwidth to be used by the HCAL to communicate with the Historian.

      • Otherwise, leave it unselected 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 lower-tier and next-tier 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 must 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.

    • High Latency Network

      • Select this option if the connection to the replication server takes place over a high-latency network (ping response times over 500 milliseconds). This option allows for longer connection timeouts. If you use this option, we recommend that you also enable compression.

      • Leave it unselected if you are not expecting connection timeouts, as this setting can negatively affect performance on a low-latency network.

12. Click Finish. The new replication server appears in the replication server list.