Page History
...
--home
- Specifies the directory in which the Agent should be installed.
--data
- Specifies the directory in which Agent data such as configuration files should be stored.
- By default the
<home>/var_<http-port>
directory is used, see options--home
and--http-port
.
--config
- Specifies the directory from which the Agent reads configuration files.
- By default the
<data>/config
directory is used, see option--data
.
--logs
- Specifies the directory to which the Agent stores log files.
- By default the
<data>/logs
directory is used, see option--data
.
--work
- Specifies the working directory of the Agent.
- By default the
<data>
directory is used, see option--data
.
--user
- Specifies the user account for the Agent daemon running as a systemd service.
- By default the account of the user running the Agent Installation Script is used.
- Should the the home or data directory be owned by an account that is different from the one running the Agent 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 Agent 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 Agent Installation Script.
- --release
- Specifies a release number such as 2.3.1 for download from the SOS web site if the
--tarball
option is not used.
- Specifies a release number such as 2.3.1 for download from the SOS web site if the
--tarball
- Optionally specifies the path to a .tar.gz file that holds the Agent 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 considershttp_proxy
andhttps_proxy
environment variables and respective settings from a.curlrc
file.
- Optionally specifies the path to a .tar.gz file that holds the Agent 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
--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 Agent's
<home>/lib/patches
directory. Note that thepatches
sub-directory will be emptied when updating an Agent installation later on. - If a backup directory is specified then an Agent'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.
- Optionally the path to the
--http-port
- Specifies the HTTP port that the Agent is operated for. The default value is
4445
. The Agent by default makes use of a data directory<home>/var_<http-port>
that will be excluded from a backup taken with the--backup-dir
option. In addition the HTTP port is used to identify the Agent Instance Start Script typically available from the<home>/bin/agent_<http-port>.sh
script and to specify the value of theJS7_AGENT_HTTP_PORT
environment variable in the script. - The port can be prefixed by the network interface, for example
localhost:4445
. - When used with the
--restart
switch the HTTP port is used to identify if the Agent is running.
- Specifies the HTTP port that the Agent is operated for. The default value is
--https-port
- Specifies the HTTPS port that the Agent is operated for. The HTTPS port is specified in the Agent Instance Start Script typically available from the
<home>/bin/agent_<http-port>.sh
script with the environment variableJS7_AGENT_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:4445
.
- Specifies the HTTPS port that the Agent is operated for. The HTTPS port is specified in the Agent Instance Start Script typically available from the
--pid-file-dir
- Specifies the directory to which the Agent 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 see JS7 - How to install for SELinux.
- Specifies the directory to which the Agent stores its PID file. By default the
--pid-file-name
- Specifies the name of the PID file. By default the file name
agent.pid
is used. - The PID file is created in the directory specified by the
--pid-file-dir
option.
- Specifies the name of the PID file. By default the file name
--instance-script
- Specifies the path to an Instance Start Script that acts as a template and that is copied to the
<home>/bin
directory. Typically the nameagent_<http-port>.sh
. is used. Users are free to choose any name for the Instance Start Script. The script has to be executable for the Agent daemon, see--user
option. Permissions of the script are not changed by the Agent Installation Script. - The Agent Installation Script will perform replacements in the Instance Start Script template for known placeholders such as
<JS7_AGENT_USER>
, for details see<home>/bin/agent_instance.sh-example
.
- Specifies the path to an Instance Start Script that acts as a template and that is copied to the
--backup-dir
- If a backup directory is specified then an Agent's existing installation directory will be added to a .tar.gz file in this directory before applying changes to the Agent installation.
- File names are created according to the pattern:
backup_js7_agent.<hostname>.<release>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.tar.gz
- For example:
backup_js7_agent.centostest_primary.2.3.1.2022-03-19T20-50-45.tar.gz
- For example:
- A backup is intended to restore files in the Agent's installation directory, not in its data directory, see
--data
. The purpose of a backup is to restore files that are replaced by the Agent Installation Script, its purpose is not to restore an Agent 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 Agent 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_agent.<hostname>.<yyyy>-<MM>-<dd>T<hh>-<mm>-<ss>.log
- For example:
install_js7_agent.centostest_primary.2022-03-19T20-50-45.log
--exec-start
- This option can be used should the Agent be started after installation. For example, when using systemd then the option
--exec-start=
"StartService"
will start the Agent 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_agent_4445"
. - 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 will start the Agent from its Instance Start Script. If specified this option overrules the--restart
switch.
- This option can be used should the Agent be started after installation. For example, when using systemd then the option
--exec-stop
- This option can be used should the Agent be stopped before installation. For example, when using systemd then the option
--exec-stop="StopService"
will stop the Agent 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_agent_4445"
. - 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 Agent from its Instance Start Script. If specified this option overrules the--restart
switch.
- This option can be used should the Agent be stopped before installation. For example, when using systemd then the option
--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_agent.centostest_primary.2022-03-20T04-54-31.log
backup_file=backup_js7_agent.centostest_primary.2.3.1.2022-03-20T04-54-31.tar.gz
- An existing file will be overwritten. It is recommended to use a unique file name such as
/tmp/return.$$.$RANDOM.properties
. - A value from the file can be retrieved like this:
backup=$(cat /tmp/return.$$.$RANDOM.properties | grep "backup_file" | cut -d'=' -f2)
- Optionally specifies the path to a file to which return values will be added in the format
...
--deploy-dir
- Specifies the path to a deployment directory that holds configuration files and sub-directories that will be copied to the
<config>
directory. A deployment directory allows to manage central copies of configuration files such asagent.conf
,private.conf
,log4j2.xml
etc. - Use of a deployment directory has lower precedence as files can be overwritten by individual options such as
--agent-conf
,--private-conf
etc.
- Specifies the path to a deployment directory that holds configuration files and sub-directories that will be copied to the
--agent-conf
- Specifies the path to a configuration file for global JS7 - Agent Configuration Items. The file will be copied to the
<config>/agent.conf
file. - Any path to a file can be used as a value of this option, however, the target file name
agent.conf
will be used.
- Specifies the path to a configuration file for global JS7 - Agent Configuration Items. The file will be copied to the
--private-conf
- Specifies the path to a configuration file for private JS7 - Agent Configuration Items. The file will be copied to the
<config>/private/private.conf
file. - Any path to a file can be used as a value of this option, however, the target file name
private.conf
will be used. - Users have a choice how to provide the required configuration:
- Download the private.conf-template-agent template, the Agent Installation Script performs replacements of placeholders in the template file from option values, for details see chapter Replacements.
- Users can manually adjust configuration items in the
private.conf
file that they specify for the Agent Installation Script, see JS7 - Agent Configuration Items.
- Specifies the path to a configuration file for private JS7 - Agent Configuration Items. The file will be copied to the
--controller-id
- Specifies the Controller ID, a unique identifier of the Controller installation. Agents will be dedicated to the Controller with the given Controller ID.
- The Controller ID is used in the Agent's
private.conf
file to specify which Controller can access a given Agent.
--controller-primary-cert
- Specifies the path to the SSL/TLS certificate of the Primary Controller instance. The Agent Installation Script extracts the distinguished name from the given certificate and adds it to the Agent's
private.conf
file to allow HTTPS connections from the given Controller using mutual authentication without the need for passwords.
- Specifies the path to the SSL/TLS certificate of the Primary Controller instance. The Agent Installation Script extracts the distinguished name from the given certificate and adds it to the Agent's
--controller-secondary-cert
- Corresponds to the
--controller-primary-cert
option and is used for the Secondary Controller instance.
- Corresponds to the
--agent-cluster-id
- Specifies the Agent Cluster ID, a unique identifier of the Agent Cluster. This is not the Primary/Secondary Director Agent ID.
- Subagents will be dedicated to the Agent Cluster with the given Agent Cluster ID.
- The Agent Cluster ID is used in the Agent's
private.conf
file to specify which pairing Director Agent instance can access the given Director Agent instance.
--directory-primary-cert
- Specifies the path to the SSL/TLS certificate of the Primary Director Agent instance. The Agent Installation Script extracts the distinguished name from the given certificate and adds it to the Agent's
private.conf
file to allow HTTPS connections from the given Director Agent instance using mutual authentication without the need for passwords.
- Specifies the path to the SSL/TLS certificate of the Primary Director Agent instance. The Agent Installation Script extracts the distinguished name from the given certificate and adds it to the Agent's
--director-secondary-cert
- Corresponds to the
--director-primary-cert
option and is used for the Secondary Director Agent instance.
- Corresponds to the
--keystore
- Specifies the path to a PKCS12 keystore file that holds the private key and certificate for HTTPS connections to the Agent.
- Users are free to specify any file name, typically the name
https-keystore.p12
is used. The keystore file will be copied to the<config>/private
directory. - If a keystore file is made available then the Agent's
<config>/private/private.conf
file has to hold a reference to the keystore location and optionally the keystore password. It is therefore recommended to use the--private-conf
option to deploy an individualprivate.conf
file that holds settings related to a keystore. - For automating the creation of keystores see JS7 - How to add SSL TLS Certificates to Keystore and Truststore.
--keystore-password
- Specifies the password for access to the keystore. Use of a keystore password is required.
- Consider use of quotes when specifying the password.
--keystore-alias
- If a keystore holds more than one private key, for example if separate pairs of private keys/certificates for server authentication and client authentication exist, then it is not determined which private key/certificate will be used. The alias name of a given private key/certificate is specified when the entry is added to the keystore. The alias name allows to indicate a specific private key/certificate to be used.
--client-keystore
- Use of this setting is optional. It can be used if separate certificates for Server Authentication and Client Authentication are used.
- The Client Authentication private key and certificate can be added to a client keystore. The location and configuration of a client keystore correspond to the
--keystore
option.
--client-keystore-password
- Specifies the password for access to the client keystore. Use of a client keystore password is required if a client keystore is used.
- Consider explanations for the
--keystore-password
option.
--client-keystore-alias
- If a client keystore holds more than one private key, for example if a number of private keys/certificates for client authentication exist, then it is not determined which private key/certificate will be used.
- Consider explanations for the
--keystore-alias
option.
--truststore
- Specifies the path to a PKCS12 truststore file that holds the certificate(s) for HTTPS connections to the Agent using mutual authentication .
- Users are free to specify any file name, typically the name
https-truststore.p12
is used. The truststore file will be copied to the<config>/private
directory. - If a truststore file is made available then the Agent's
<config>/private/private.conf
file has to hold a reference to the truststore location and optionally the truststore password. It is therefore recommended to use the--private-conf
option to deploy an individualprivate.conf
file that holds settings related to a truststore. - For automating the creation of truststores see JS7 - How to add SSL TLS Certificates to Keystore and Truststore.
--truststore-password
- Specifies the password for access to the truststore. Use of a password is recommended as it is not primarily intended to protect access to the truststore. The password is intended to allow verification that truststore entries have been added using the same password.
- Consider use of quotes when specifying the password.
--java-home
- Specifies the Java home directory that will be made available to the Agent from the
JAVA_HOME
environment variable specified with the Agent Instance Start Script typically available from the./bin/agent_<http-port>.sh
script.
- Specifies the Java home directory that will be made available to the Agent from the
--java-options
- Specifies the Java options that will be made available to the Agent from the
JAVA_OPTIONS
environment variable specified with the Agent Instance Start Script typically available from the./bin/agent_<http-port>.sh
script. - Java options can be used for example to specify Java heap space settings for the Agent.
- If more than one Java option is used then the value has to be quoted, for example
--java-options="-Xms256m -Xmx512m"
.
- Specifies the Java options that will be made available to the Agent from the
--service-dir
- Specifies the systemd service directory to which the Agent's service file will be copied if the
--make-service
switch is used. - By default the
/usr/lib/systemd/system
directory will be used. Users can specify an alternative location.
- Specifies the systemd service directory to which the Agent's service file will be copied if the
--service-file
- Specifies the path to a systemd service file that acts as a template and that will be copied to the Agent's
<home>/bin
directory. Users are free to choose any file name as a template for the service file. The resulting service file name will beagent_<http-port>.service
. - The Agent Installation Script will not perform replacements in the service file to update paths and the port to be used, for etc., for details see
./bin/agent.service-example
.
- Specifies the path to a systemd service file that acts as a template and that will be copied to the Agent's
--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_agent_<http-port>
will be used.
- Specifies the name of the systemd service that will be created if the
...
-h | --help
- Displays usage.
--force-sudo
- Specifies that
sudo
is used when performing operations on directories. This switch is required if the home or data directory is not owned by the user account running the Agent Installation Script.
- Specifies that
--active
- This setting is used for Director Agents only. It specifies that the Director Agent instance should act as the active node in a Director Agent Cluster during initial operation.
- This setting is not required for installation of a Primary Director Agent in an Agent Cluster. It can be used to revert a Secondary Director Agent to a Primary Director Agent.
--standby
- This setting is used for Director Agents only. It specifies that the Director Agent instance should act as the standby node in a Director Agent Cluster during initial operation.
- This setting is required when installing a Secondary Director Agent instance in an Agent Cluster.
--no-yade
- Excludes the YADE file transfer utility from the Agent installation.
- YADE is available from the
yade
sub-directory of the Agent's<home>
directory. If this switch is used then an existingyade
sub-directory will be removed and YADE will not be copied from the installation tarball to the Agent's<home>
directory.
--no-install
- Specifies if the Installation Script should be used to update configuration items without changes to the binary files of the installation.
In fact no installation is performed but configuration changes as for example specified with the--keystore
option will be applied.
- Specifies if the Installation Script should be used to update configuration items without changes to the binary files of the installation.
-use-install
Resuses an existing Agent installation. No installation files are specified as with the
--release
or--tarball
parameters. Instead, the new Agent's data directory and the respective service will be created.
--uninstall
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and to remove the
<home>
and<data>
directories.
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and to remove the
--uninstall-home
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and removes the
<home>
directory only.
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and removes the
--uninstall-data
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and preserves the
<data>
directory only.
- Uninstalls the Agent including the steps to stop and to remove a running Agent service and preserves the
--service-selinux
- Updates the systemd service file for compliance with SELinux, see JS7 - How to install for SELinux.
--show-logs
- Displays the log output created by the script if the
--log-dir
option is used.
- Displays the log output created by the script if the
--make-dirs
- If directories are missing that are indicated with the
--home
,--backup-dir
or--log-dir
options then they will be created.
- If directories are missing that are indicated with the
--make-service
- Specifies that a systemd service should be created for the Agent. The service will be created from the
--service-name
option or its default value.
- Specifies that a systemd service should be created for the Agent. The service will be created from the
--move-libs
- For an existing Agent installation the
lib
sub-directory includes .jar files that carry the release number in their file names. If replaced by a newer version thelib
directory has to be moved or removed. This switch tries to move the directory to a previous version number as indicated from the.version
file in the Agent's home directory, for example to renamelib
tolib.2.3.1
. - Files in the
lib/user_lib
sub-directory are preserved.
- For an existing Agent installation the
--remove-journal
- If Agents have been installed for the wrong operating mode (standalone, clustered) then the Agent's journal in the
JS7_AGENT_DATA/state
directory can be removed. This operation removes any orders submitted to an Agent and requires the Agent to be re-registered to a Controller.
- If Agents have been installed for the wrong operating mode (standalone, clustered) then the Agent's journal in the
--restart
- Stops a running Agent before installation and starts the Agent after installation using the Agent's Instance Start Script. This switch can be used with the
--abort
and--kill
switches to control the way how the Agent is terminated. This switch is ignored if the--exec-start
or--exec-stop
options are used.
- Stops a running Agent before installation and starts the Agent after installation using the Agent's Instance Start Script. This switch can be used with the
--abort
- Aborts a running Agent and kills any running tasks including child processes if used with the
--restart
switch. Aborting an Agent includes to terminate the Agent in an orderly manner that allows to close files consistently.
- Aborts a running Agent and kills any running tasks including child processes if used with the
--kill
- Kills a running Agent and any running tasks if used with the
--restart
switch. This includes killing child processes of running tasks.
- Kills a running Agent and any running tasks if used with the
...
Overview
Content Tools