Install Multiple Data Collectors for Cloud

About this task

The install program typically allows only the install of one specific collector with a single source and destination. After the install, it is possible to run additional collectors of same type. The following example describes how to installing multiple data collector for Server to Cloud. The configuration involves two steps:
  • Creating the service
  • Creating the registry keys

Step-1 Creating the service

Procedure

  1. Start a command prompt as an administrator.
  2. From command prompt, register the service:
    NOTE: binPath will depend on the installation
    • sc create "S2C_01" binpath= "C:\ Program Files (x86)\GE Digital\Historian Server to Server Collector\Server\ihServerToServerCollector.exe REG=S2C_01" DisplayName= "Historian Server to Cloud 1" start= auto

      [you should see CreateService SUCCESS message]

    • Repeat Step 2 as needed to create additional instances if needed.

      For example, to create a second instance:

    sc create "S2C_02" binpath= "C:\ Program Files (x86)\GE Digital\Historian Server to Server Collector\Server\ihServerToServerCollector.exe REG=S2C_02" DisplayName= "Historian Server to Cloud 2" start= auto

    [you should see CreateService SUCCESS message]

  3. Verify the "Historian Server to Cloud 1" and "Historian Server to Cloud 2" are visible in the service control.
    Step-2 Creating the registry keys:
    1. The following registry entries are required to start Server to Server Collector.
      1. Run the ?regedit command to open the ?Registry Editor ?. Navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GE Digital\iHistorian\Services\ServerToServerCollector\S2C_01

        And

        Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GE Digital\iHistorian\Services\ServerToServerCollector\S2C_02
      2. Create/Modify the following ?Keys as needed.

      "INTERFACENAME"="HistorianServerToCloud2"

      "HISTORIANNODENAME"=" cloud|wss://xx/v1/stream/messages|configServer=xx|identityissuer=xx.predix.io/oauth/token|clientid=xx|" "General3"="DataSourceHistorian"
    2. If collector tag list is coming from an Offline Tag Configuration File, create a string registry called: OfflineTagConfigurationFile and set the path to the xml file where tag list is saved. It is recommended to create a unique file per collector.

      For Server to Server Collector the typical value of OfflineTagConfigurationFile is: C:\Program Files (x86)\GE Digital\Historian Server to Server Collector\Config\ S2C_01_Offline_Config.xml

    3. Start the Server to Cloud Collector to create the full set of registry keys.