Installation with Spectrum¶

Installation¶

The OneClick Extension is installed in the form of a Spectrum management module. Since additional parameters are required for the installation, the installation is started via the setup.sh script.

Copy VCD-DCS-OneClickExt_<app_version>_<spectrum_version>.tar to the destination OneClick server(s) and unpack it
Start the installation: Start setup.sh in the VCD directory:

$ ./setup.sh
Installing to C:/opt/spectrum ...

    OneClickExt Server is win10dev-ww (y/n)? y
    Enter the RMI Port (1025-65535)? 16016
    Enter the RMI Connection Port (1025-65535)? 16017
    OneClickExt Server = win10dev-ww, RMI Port = 16016, RMI Conn Port = 16017 (y/n)?

    Hostname of the Main Location Server? win10dev-ww
    Hostname of the Backup Location Server? win10dev-ww
    SpectroSERVER is win10dev-ww (y/n)? y
    SpectroSERVER is win10dev-ww, Location Servers are win10dev-ww / win10dev-ww (y/n)? y

OneClickExtension setup:
  MainLocation Server = win10dev-ww
  BackupLocation Server = win10dev-ww
  SpectroSERVER = win10dev-ww
  Is primary = Y
  Autostart Ticket = Y
  OneClickExt Host = win10dev-ww
  RMI Port = 16016
  RMI Connection Port = 16017

saving /tmp/dcssetup.config ...
starting installer ...

Post-installation¶

After installation, a few settings still need to be adjusted:

After installation, checkOCext.pl (idb-ticket) checks whether the OneClick Extension is loaded in OneClick and corrects this if necessary. Alternatively, you can also manually integrate the extension into the Spectrum call (oneclick.jnlp): To do this, copy the file SPECROOT/tomcat/webapps/spectrum/oneclick.jnlp.ext to SPECROOT/tomcat/webapps/spectrum/oneclick.jnlp.
When upgrading from a previous version, the new properties are installed as oneclickext_<version>.props. These must either be renamed or their content must be integrated into the existing file.
Create menu. The test script menu from the conf directory (custom_menu_config_script_launcher.xml) can be used as an example.