Creating a Second Orbit Updater

Creating a Second Orbit Updater

Some partner configurations will have more that one Orbit installation.

This article describes the process for setting up additional Orbit Updaters to allow side by side Orbit installations on a single web server. This guide assumes that Orbit is already configured and running and all necessary prerequisites are therefore installed.

Create OrbitUpdaterSetup.msi


To be able to have an additional FastStats Orbit Updater service, it is necessary to use the Setup Manager (which can be found in the FastStatsEnterprise.zip, available in the Software Downloads section of our website portal) to create a unique FastStats Orbit Updater Installer.

Copy MSI

Copy the original OrbitUpdaterSetup.msi and rename the copy. In this example it has been named OrbitUpdaterSetupHolidays.msi


Setup Manager

Run Setup Manager and open the new .msi

In Properties, update the Product Name, Product Description and check the Base installer identity on Product Name checkbox



In Directory Structure, rename the directory

In Services, rename the Short Name and Display Name settings






From the File choose Save

Install New FastStats Orbit Updater

Run the installer and follow the instructions



It will open the FastStats Orbit Updater Configurator as part of the installation process

Within the API settings, update the Virtual path and Base URL to have the new structure, in this case adding Holidays. Also make sure that the connection string to the Orbit DB is correct.



Within the UI settings update the Virtual path and Base URL to have the new structure.



There are no changes needed within the Login Service, Updater and Advanced settings.

You might need to make the same changes to the URLs in the Connect API, Connect UI, Responses API and Chat API sections e.g.


Close and complete the installation.


Check Installation

The service will have automatically started:



And the new files will be in the configured place



Continue to set up the Orbit install as you would normally, just remember to make sure that you reference the correct Orbit location.

For example within the Orbit API URL in the FastStats Service configuration:




    • Related Articles

    • Cannot access Orbit Audiences in FastStats and PeopleStage

      If the system has been configured correctly then you should be able to access Orbit Audiences from within FastStats and PeopleStage. This is useful because you might have an Audience created within Orbit which you want to refer to in a FastStats ...

    • Adding Communications tables for Campaign Objectives

      Campaign Objectives in Orbit require response attribution. In order to report on this, the FastStats system needs to have the standard PeopleStage/Campaign tables included. You can add these to an existing design by using the Merge functionality ...

    • Combining Table Results in Orbit using a CubeLookup Expression

      Sometimes it is useful to be able to get results from a Table in Orbit and use them in another Table. Within Orbit, it isn't currently possible to refer to results in one tile within another one. However, we can use a combination of some powerful ...

    • Changing the default email address for the Orbit Administrator

      By default the Administrator user for each Orbit system is created with an email address of support@apteco.com This is done for assistance and reporting purposes e.g. for assistance when setting a new system up. A side effect of this is that any ...

    • Error Message with Login Service on new Orbit setup

      A user queried a message received in Orbit whilst moving a system to AWS. Everything seemed to be working correctly so he questioned the message given: Our answer was that the Login Service is something we use as part of the SSO login process. ...