Page History

...

• --home
  • Specifies the directory in which the Controller should be installed.
• --data
  • Specifies the directory in which the Controller data such as configuration files should be stored.
  • If this option is omitted then the <home>/var directory will be used, see option --home.
• --config
  • Specifies the directory from which the Controller reads configuration files.
  • By default the <data>/config directory is used, see option --data.
• --logs
  • Specifies the directory to which the Controller stores log files.
  • By default the <data>/logs directory is used, see option --data.
• --user
  • Specifies the user account for the Controller daemon.
  • By default the account of the user running the Controller Installation Script is used.
  • Should the the home or data directory be owned by an account that is different from the one running the Controller Installation Script then consider use of the --home-owner and --data-owner options.
• --home-owner
  • Optionally specifies the user account and group that should own the home directory. By default the home directory is created and owned by the current user account.
  • Syntactically a user account and optionally a group can be specified, for example --home-owner=sos or --home-owner=sos:sos. If the group is not specified then a group with the name of the user account is assumed.
  • Use of this option requires sudo permissions for the user account that runs the Controller Installation Script.
• --data-owner
  • Optionally specifies the user account and group that should own the data directory. By default the data directory is created and owned by the current user account.
  • Syntactically a user account and optionally a group can be specified, for example --data-owner=sos or --data-owner=sos:sos. If the group is not specified then a group with the name of the user account is assumed.
  • Use of this option requires sudo permissions for the user account that runs the Controller Installation Script.
• --controller-id
  • Specifies the Controller ID, a unique identifier of the Controller installation. If more than one Controller should be registered with JOC Cockpit then they have to use different Controller IDs.
  • If two Controller instances should work in a Cluster then they have to use the same Controller ID.
• --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 Controller installation or patch files. If this option is not used the installation or patch tarball will be downloaded from the SOS web site for the release indicated with the --release option.
  • Download is performed with curl that considers http_proxy and https_proxy environment variables and settings from a .curlrc file.
• --patch
  • A patch is identified by an issue key in the Change Management System, for example JS-1984.
  • Patches are downloaded from the SOS web site if the --tarball option is not used.
  • Patches are added to the Controller's <home>/lib/patches directory. Note that the patches sub-directory will be emptied when updating a Controller installation later on.
  • If a backup directory is specified then a Controller's existing installation directory will be added to a .tar.gz backup file in this directory.
• --patch-jar
  • Optionally specifies the path to a .jar file that holds the patch if a patch is provided in this format.
• --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.
• --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 option 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.
• --http-port
  
  • Specifies the HTTP port that the Controller is operated for. The default value is 4444. The HTTP port is used to specify the value of the JS7_CONTROLLER_HTTP_PORT environment variable in the Controller Instance Start Script.
  • The port can be prefixed by the network interface, for example localhost:4444.
  • When used with the --restart switch the HTTP port is used to identify if the Controller instance is running.
• --https-port
  • Specifies the HTTPS port that the Controller is operated for. The HTTPS port is specified in the Controller Instance Start Script typically available from ./bin/controller_instance.sh. with the environment variable JS7_CONTROLLER_HTTPS_PORT. Use of HTTPS requires a keystore and truststore to be present, see --keystore and --truststore options.
  • The port can be prefixed by the network interface, for example batch.example.com:4444.
• --pid-file-dir
  • Specifies the directory to which the Controller stores its PID file. By default the <data>/logs directory is used.
  • When using SELinux then it is recommended to specify and to create the /var/run/js7 directory, see JS7 - How to install for SELinux.
• --pid-file-name
  • Specifies the name of the PID file. By default the file name controller.pid is used.
  • The PID file is created in the directory specified by the --pid-file-dir option.
• --instance-script
  • Specifies the path to a script that acts as the Instance Start Script and that is copied to the bin directory. Typically the name controller_instance.sh. is used. Users are free to choose any name for the script. The script has to be executable for the Controller daemon, see --user. Permissions of the script are not changed by the Controller Installation Script.
  • The Controller Installation Script will perform replacements in the Instance Start Script template for known placeholders such as <JS7_CONTROLLER_USER>, for details see ./bin/controller_instance.sh-example.
• --backup-dir
  • If a backup directory is specified then an Controller's existing installation directory will be added to a .tar.gz file in this directory.
  • File names are created according to the pattern: backup_js7_controller.<hostname>.<release>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.tar.gz
    • For example: backup_js7_controller.centostest_primary.2.3.1.2022-03-19T20-50-45.tar.gz
  • A backup is intended to restore files in the Controller's installation directory, not in its data directory, see --data. The purpose of a backup is to restore files that are replaced by the Controller Installation Script, its purpose is not to restore a Controller installation that otherwise is corrupted or removed. No backup will be taken if one of the --uninstall options is used.
• --log-dir
  • If a log directory is specified then the Controller Installation Script will write information about processing steps to a log file in this directory.
  • File names are created according to the pattern: install_js7_controller.<hostname>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.log
  • For example: install_js7_controller.centostest_primary.2022-03-19T20-50-45.log
• --exec-start
  • This option can be used should the Controller be started after installation. For example, when using systemd then the option --exec-start="StartService" will start the Controller 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_controller".
  • 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 the use of the --restart switch which starts the Controller from its Instance Start Script. If specified this option will overrule the --restart switch.
• --exec-stop
  • This option can be used should the Controller be stopped before installation. For example, when using systemd then the option --exec-stop="StopService" will stop the Controller 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_controller".
  • 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 the use of the --restart switch which stops the Controller from its Instance Start Script. If specified this option will overrule the --restart switch.
• --return-values
  • Optionally specifies the path to a file to which return values will be added in the format <name>=<key>. For example:
    
    • log_file=install_js7_controller.centostest_primary.2022-03-20T04-54-31.log
    • backup_file=backup_js7_controller.centostest_primary.2.3.1.2022-03-20T04-54-31.tar.gz
  • Any 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)

...