Change the Destination Server of a Collector

Before you begin

  1. Ensure that Historian is installed on the new destination server to which you want the collector to send data.
  2. Ensure that the collector whose destination server you want to change is running.

Procedure

  1. Access Configuration Hub.
  2. In the NAVIGATION section, under the Configuration Hub plugin for Historian, select Collectors.
    A list of collectors appears.
    Tip: You can filter the collectors by the system name.
  3. Right-click the collector instance whose destination server you want to change (or select ), and then select Change Destination Server.
    The Change Destination Server: <collector name> window appears. The COLLECTOR MACHINE, CURRENT RUNNING MODE, and CURRENT DESTINATION SERVER fields are populated and disabled.
  4. In the NEW RUNNING MODE field, select one of the following options:
    • Service: Select this option if you want to start the collector as a Windows service using the credentials of the local user (that is, the currently logged-in user). If you select this option, the USERNAME and PASSWORD fields are disabled.
    • Command Line: Select this option if you want to start the collector in the command-line mode. If you select this option, you must enter values in the USERNAME and PASSWORD fields.
  5. In the NEW DESTINATION SERVER field, enter the host name or IP address of the new destination server to which you want the collector to send data.
  6. In the USERNAME and PASSWORD fields, enter the credentials to access the new destination server.
  7. Select Change Server.
    The destination server of the collector is changed, and the collector is stopped.

What to do next

  1. Update the network message compression of the collector by modifying the collector instance using Configuration Hub.
  2. Reconfigure the collector properties using Historian Administrator.
  3. Restart the collector.