Multiple adTempus Server Instances

You can run multiple instances of the adTempus server on the same computer. Each instance is a separate copy of the adTempus software, with its own database, settings, and other data, that runs independently of all other instances.

For example, if your main adTempus instance is running your production jobs, you could create a second instance for testing new versions of jobs. You can then use the Export tool to copy jobs from the test instance to the production instance.

The first instance of adTempus is usually the "Default" instance and can be referred to without its instance name.

In adTempus 4, all instances shared the same software and so all ran the same version of adTempus. Beginning with version 5, each instance is a separate installation of the software that is completely independent of other instances. This allows you to run different versions of the server on the same computer. If you are upgrading existing instances from version 4, see the Upgrading topic.

What is an Instance?

Each adTempus instance runs as a separate copy of the adTempus service (each adTempus instance appears as a separate service in the Windows Service Manager). Because each instance runs as a separate service, it is isolated from other instances: you can stop or start each instance independently without affecting the other instances. Each instance also has its own database and other data.

Requirements for Multiple Instances

You can create as many instances on a single computer as your hardware can support. The practical limit will depend on memory and processor power.

In order to allow all instances to use the same port number for communications, the Net.Tcp Port Sharing Service (installed by the Microsoft .NET Framework) must be enabled and started. adTempus setup will handle this for you.

If the adTempus service fails to start with an error saying that the TransportManager failed to listen using the NetTcpPortSharing service, stop all adTempus instances, start (or restart) the Net.Tcp Port Sharing Service, and then start the adTempus instances again. This can happen if the Port Sharing service was not running, or was started after an instance was already running (for example, if the default instance was running when you created a new instance).

Running Without the Port Sharing Service

If system policies prevent you from using the Net.Tcp Port Sharing Service, you can configure adTempus not to use it. You will then be able to run more than one instance only if each instance uses a different port number. To disable port sharing:

  1. Run the Registry Editor and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.
  2. For each instance key (named "adTempus$instancename"), edit the DependOnService value and remove the line that reads "NetTcpPortSharing".
  3. Go to the key HKEY_LOCAL_MACHINE\SOFTWARE\Arcana Development\adTempus\GlobalOptions and set the ServiceHost:EnablePortSharing value to 0.
  4. Start the adTempus service.

Creating Additional Instances

To create a new instance, run the adTempus setup program either directly or by choosing the Modify option for adTempus in Add/Remove Programs. Then select Add an adTempus Server Instance. This will launch the Setup Wizard to install and configure the instance.

Managing Instances

When you have multiple instances installed and run one of the server tools on the Start menu (Database Configuration Wizard, Database Utility, Server Configuration Tool) you will be prompted to select the instance to manage before the tool launches.

Removing Instances

To remove an instance, choose the Modify option for adTempus in Add/Remove Programs to start the Setup Navigator. Then select Uninstall adTempus from the Maintenance tab to start the Uninstall Wizard, where you can choose the instance(s) to remove.

Connecting to Instances

To connect to an instance other than the Default, specify the instance name in the Server Connection Properties window when you create a new Server Connection in the Console.