Skip to content
  • There are no suggestions because the search field is empty.

How-To: Run Multiple Instances of HighByte Intelligence Hub as Windows Services

Configure multiple HighByte Intelligence Hub instances to run simultaneously on a single Windows machine by setting up unique Windows services

What Does This Article Cover?

This guide explains how to configure and run multiple instances of HighByte Intelligence Hub as separate Windows services. By following these steps, users can set up multiple hub instances with unique service names, allowing for concurrent operation.

Prerequisites

  • Administrative access to the Windows machine.
  • HighByte Intelligence Hub installation files.
  • Familiarity with batch file (.bat) editing.


Steps:

Step 1: Duplicate and Rename Service Files

  1. Navigate to the runtime/service folder within your HighByte Intelligence Hub directory.
  2. Copy service-installer-windows.exe and service-installer-windows.xml.
  3. Rename each copied file to ensure uniqueness. For example:
    • service-installer-windows2.exe
    • service-installer-windows2.xml

Step 2: Edit the XML Configuration File

  1. Open the newly created XML file (e.g., service-installer-windows2.xml) in a text editor.
  2. Update the following fields to make them unique:
    • ID: Change <id>HighbyteIntelligenceHubRuntime</id> to a unique identifier, like <id>HighbyteIntelligenceHubRuntime2</id>.
    • Name: Update <name>HighByte Intelligence Hub Runtime</name> to differentiate this instance, e.g., <name>HighByte Intelligence Hub Runtime2</name>.
    • Description: Modify <description> to reflect the purpose of this instance, such as <description>HighByte Intelligence Hub Runtime service2</description>.
    <service>
        <!-- ID of the service. It should be unique across the Windows system -->
        <id>HighbyteIntelligenceHubRuntime2</id>
        
        <!-- Display name of the service -->
        <name>HighByte Intelligence Hub Runtime2</name>
        
        <!-- Service description -->
        <description>HighByte Intelligence Hub Runtime service2</description>

     
  3. Save the file.

Step 3: Modify Batch Files for Installation and Uninstallation

  1. Open the install-windows-service.bat and uninstall-windows-service.bat files in a text editor.
  2. Replace any instances of service-installer-windows.exe with the newly renamed file (e.g., service-installer-windows2.exe).
    @echo off

    echo Installing HighByte Intelligence Hub Runtime Service

    service-installer-windows2.exe install --no-elevate

    service-installer-windows2.exe start --no-elevate

    timeout 20

     

Step 4: Install and Start the New Service

  1. Run the modified install-windows-service.bat to install the new instance as a Windows service.
  2. Use service-installer-windows2.exe to start the service if it doesn’t automatically start.

Step 5: Verify the Service Status

  1. Open the Services management console (Run > services.msc).
  2. Confirm that both instances (e.g., HighByte Intelligence Hub Runtime and HighByte Intelligence Hub Runtime2) are listed and running.

Step 6: Uninstalling the Additional Service

If you need to uninstall the additional HighByte Intelligence Hub instance, follow these steps:

  1. Open the modified uninstall-windows-service.bat file (for example, uninstall-windows-service2.bat) in the runtime/service folder.

  2. Ensure that the file contains the correct executable references for the additional instance, as shown below:

    @echo off
    echo Uninstalling HighByte Intelligence Hub Runtime2 Service
    service-installer-windows2.exe stop --no-elevate
    service-installer-windows2.exe uninstall --no-elevate
    timeout 5
  3. Run the modified uninstall-windows-service.bat file to stop and remove the additional service from your Windows Services.

  4. Verify that the service has been removed:

    • Open Services (Run > services.msc).
    • Confirm that the additional service (e.g., HighByte Intelligence Hub Runtime2) is no longer listed.

Troubleshooting

  • Service Not Starting: Ensure the service names and IDs in the XML file are unique. Conflicts in names or IDs can prevent services from starting.
  • Log File Conflicts: Verify that each instance has a unique log directory defined in <logpath> within the XML file if needed.