Overview

With OneSetup, Collab developed a single setup application for all the OneContact CC Server components. Until now, when installing several components on the same machine the user had to run several installers and input the same parameters several times. With this Server Setup application, the installation and upgrade processes are greatly improved.

The installation packages are downloaded from a repository, decoupling the OneSetup application from the various installation packages and their versions.

OneSetup is packaged as a self-extracting rar. To start the installation process you have to:

  1. Run the Setup.exe application.

  2. The package contents are uncompressed to a directory on program files (C:\Program File\Collab\OneSetup).

  3. The Setup.exe is launched, upon user confirmation:
    OneSetup_launch.png

 

To install OneSetup silently and without running the application, use the following command line over the self extracting package: 

setup.exe -s norun

Note: The -s is for the silent installation and the -s norun passes the “norun” parameter to the setup.exe application causing it to exit immediately.

 

Two shortcuts (one for the GUI and another for the CLI, with a command prompt) are also created on the start menu:

OneSetup_icons.png

 

The OneSetup application has four main features:

  • Install – Installs a new instance of OneSetup components.
  • Upgrade or Repair – Upgrades or repairs a OneSetup instance.
  • Uninstall – Uninstalls a OneSetup instance.
  • Download – Downloads packages to the local disk in order to perform an offline installation.

 

OneContact CC setup packages allow several side-by-side installations, on the same machine. These installations are here designated as install instances and they are also supported by the OneSetup application, either on new installations or those done previously by the existing packages. In fact, the existing packages continue to exist and can be used as before.

In the case of the web applications the instance is defined by the following pattern:

component[(component_instance)](version)

For the other installations the pattern is:

component[(instance)](version)

Note: If no instance name is specified the product is installed on the default instance – identified by the empty string.