Page History

...

• • --setup-dir
    • Specifies the directory in which the installer for the JOC Cockpit should be extracted. This is not the JOC Cockpit installation directory but the directory that holds installer files.
  • --response-dir
    
    • Specifies the directory that holds a copy of  the JOC Cockpit installer joc_install.xml response file and optionally related files. This file is available after extraction of the installer tarball and specifies options for installation of the JOC Cockpit. Files in the response directory are copied to the working directory specified with the --setup-dir option. and are applied when invoking the installer by ./setup.sh -u joc_install.xml, see JS7 - JOC Cockpit - Headless Installation on Linux and Windows.
    • Users should keep their copy of the response file and specify the directory with this command line option. Response files can be re-used within the same minor release of the JOC Cockpit, for example when updating from release 2.2.1 to 2.2.4. When updating, for example, from release 2.2.x to 2.3.x it is recommended to check from the installer tarball if a newer version of the file is available.
    • Users should note that the response file can hold references to a license file and to a JDBC Driver .jar file. The JOC Cockpit setup is executed from the working directory specified with the --setup-dir option. Paths in the joc_install.xml response file can be used relative to the working directory, for example using sos.pem for a license file without specifying a directory if the license file is available in the response directory as it will be copied to the working directory.
  • --release
    • Specifies a release number such as 2.3.1 for download from the SOS web site if the --tarball option is not used.
  • --tarball
    • Optionally specifies the path to a .tar.gz file that holds the JOC Cockpit installation files. If this option is not used the installer tarball will be downloaded from the SOS web site for the release indicated with the --release option.
    • Download is performed with curl which takes account of http_proxy and https_proxy environment variables and the relevant settings from a .curlrc file.
  • --home
    • Specifies the directory in which the JOC Cockpit should be installed.
    • This option overwrites the JOC Cockpit installation directory specified in the joc_install.xml response file with the <installpath> element.
  • --data
    • Specifies the directory in which the JOC Cockpit installs configuration files. The configuration directory is accessible from the jetty_base symlink in the JOC Cockpit home directory.
    • This option overwrites the JOC Cockpit configuration directory specified in the joc_install.xml response file with the <entry key="jettyBaseDir" value="..."/> element.
  • --user
    • The JOC Cockpit joc_install.xml response file holds the runningUser setting that optionally specifies the user account of the JOC Cockpit daemon service. This setting allows to take precedence over the response file setting.
    • The user account specified will be used for the JOC Cockpit installation. 
  • --title
    • The title of the JOC Cockpit instance is displayed with its dashboard. It serves to distinguish JOC Cockpit instances operated as a cluster.
    • This option has precedence over the respective setting specified in the joc_install.xml response file with the <entry key="jocTitle" value="..."/> element.
  • --security-level
    • The JOC Cockpit is operated in one of the security levels low, medium, high, see JS7 - Security Architecture. By default the low security level is used.
    • This option has precedence over the respective setting specified in the joc_install.xml response file with the <entry key="securityLevel" value="..."/> element.
  • --dbms-file
    • Optionally specifies the path to a Hibernate configuration file that includes settings to access the JS7 - Database.
    • This option has precedence over the respective setting specified in the joc_install.xml response file with the <entry key="hibernateConfFile" value="..."/> element.
  • --dbms-init
    • Specifies the point in time when database objects will be created:
      • byInstaller: Database objects will be created during installation of JOC Cockpit.
      • byJoc: Database objects will be created on start-up of JOC Cockpit, for example when used for Containers.
      • off: Database objects will not be created. This assumes that users create database objects on their own before running JOC Cockpit. The JOC Cockpit installation tarball includes the db sub-directory that holds *.sql files for the respective DBMS that can be used to populate the JS7 - Database independently from installing JOC Cockpit.
  • --dbms-driver
    • Specifies the path to the JDBC Driver *.jar file used for access to the DBMS. See JS7 - Database to identify JDBC Drivers that ship with JS7.
  • --patch
    • A patch is identified by the release number to which it is applied which is specified with the --release option and by
      • the JOC Cockpit security level: low, medium, high,
      • a sequential number such as patch-1, patch-2.
      • A patch is specified as --patch=low.patch-1, --patch=low.patch-2, --patch=medium.patch-1 etc.
    • For JOC Cockpit patches are consolidated, i.e. patch-2 includes any patches of patch-1.
    • Patches are downloaded from the SOS web site if the --tarball option is not used.
    • Patches are added to the JOC Cockpit's JETTY_BASE/webapps/joc/WEB-INF/classes directory. When updating JOC Cockpit later on then the classes sub-directory will be emptied.
    • If a backup directory is specified then a JOC Cockpit's existing installation directory will be added to a .tar.gz file in this directory.
  • --license-key
    • Optionally the path to a license key file is specified. Customers with a Commercial License receive the license key file from SOS in .pem or .crt format.
    • For details see JS7 - How to apply a JS7 License Key.
    • This option is an alternative to specifying the license key file with the joc_install.xml response file, see --response-dir option.
  • --license-bin
    • Optionally the path to the js7-license.jar binary file is specified that includes code that is available for use with a Commercial License only, see JS7 - How to apply a JS7 License Key.
    • Should this argument be omitted and a license key file be specified with the --license-key option then the binary file is downloaded from the SOS Web Site, see JS7 - Download.
    • This option is an alternative to specifying the license key file with the joc_install.xml response file, see --respons-dir option. If the response files specifies a license key then the binary file for licensed code is automatically installed.
  • --http-port
    • Specifies the HTTP port that the JOC Cockpit is operated for. This argument takes precedence over the port setting in the joc_install.xml response file.
    • Users are discouraged to enable both HTTP and HTTPS protocols as it undermines security to operate JOC Cockpit for both protocols.
    • The port can be prefixed by the network interface, for example joc.example.com:4446.
    • When used with the --restart switch, the HTTP port is used to determine if JOC Cockpit is running.
  • --https-port
    • Specifies the HTTPS port that the JOC Cockpit is operated for. This argument takes precedence over the port setting in the joc_install.xml response file.
    • Users are discouraged to enable both HTTP and HTTPS protocols as it undermines security to operate JOC Cockpit for both protocols.
    • The port can be prefixed by the network interface, for example joc.example.com:4448.
    • Use of HTTPS connections requires additional settings, see --ini , --keystore and --truststore options.
    • When used with the --restart switch, the HTTPS port is used to determine if JOC Cockpit is running.
  • --backup-dir
    • If a backup directory is specified then an existing JOC Cockpit's installation directory will be added to a .tar.gz file in this directory.
    • File names are created according to the pattern: backup_js7_joc.<hostname>.<release>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.tar.gz
    • For example: backup_js7_joc.centostest_primary.2.3.1.2022-03-19T20-50-45.tar.gz
  • --log-dir
    • If a log directory is specified then the installer script logs information about processing steps to a log file in this directory.
    • File names are created like this: install_js7_joc.<hostname>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.log
    • For example: install_js7_joc.centostest_primary.2022-03-19T20-50-45.log
  • --service-dir
    
    • Specifies the systemd service directory to which the JOC Cockpit's service file will be copied if the --make-service switch is used.
    • By default the a/usr/lib/systemd/system will be used. Users can specify an alternative location.
  • --service-file
    
    • Specifies the path to a systemd service file that acts as a template and that is copied to the JOC Cockpit's <home>/jetty/bin directory.
    • Users are free to choose any file name as a template for the service file. The resulting service file name will be joc.service.
    • The JOC Cockpit Installer Script will perform replacements in the service file to update paths to be used.
  • --service-name
    
    • Specifies the name of the systemd service that will be created if the --make-service switch is used.
    • By default the service name js7_joc will be used.
  • --exec-start
    • This option can be used should JOC Cockpit be started after installation. For example, when using systemd then the option --exec-start="StartService" will start the JOC Cockpit service provided that the related systemd service has been created manually or by use of the --make-service switch. Alternatively users can specify individual commands, for example --exec-start="sudo systemctl start js7_joc".
    • For systemd service files see the JS7 - systemd Service Files for automated Startup and Shutdown with Unix Systems article.
    • This option is an alternative for use of the -restart switch that starts the JOC Cockpit from its Start Script. If specified this option overrules the --restart switch.
  • --exec-stop
    • This option can be used should JOC Cockpit be stopped before installation. For example, when using systemd then the option --exec-stop="StopService" will stop the JOC Cockpit service provided that the related systemd service has been created manually or by use of the --make-service switch. Alternatively users can specify individual commands, for example --exec-stop="sudo systemctl stop js7_joc".
    • For systemd service files see the JS7 - systemd Service Files for automated Startup and Shutdown with Unix Systems article.
    • This option is an alternative to use of the -restart switch that stops the JOC Cockpit from its Start Script. If specified this option overrules the --restart switch.
  • --return-values
    • Optionally specifies the path to a file which return values will be added to in the format <name>=<key>. For example:
      • log_file=install_js7_joc.centostest_primary.2022-03-20T04-54-31.log
      • backup_file=backup_js7_joc.centostest_primary.2.3.1.2022-03-20T04-54-31.tar.gz
    • An existing file will be overwritten. It is recommended that a unique file name such as /tmp/return.$$.$RANDOM.properties is used.
    • A value from the file can be retrieved like this:
      • backup=$(cat /tmp/return.$$.$RANDOM.properties | grep "backup_file" | cut -d'=' -f2)

...