Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Installation Parameters updated

...

This article describes the use of the JobScheduler Universal Agent Batch Installer on a Linux server, working from a Windows system.

Note that the Batch Installer is only available for the current JobScheduler Universal Agent version.

Installation Procedure

General requirements:

...

  • Open your batch_installer_config_file.xml configuration file in the XML Editor.
    • Assign the scheduler_universal_agent_installations.xsd schema, which will also be located in the SCHEDULER_DATA/config/batch_installer folder.

The root XML element of the Batch Installer configuration file is the <installations> element. This contains an <installation> element for each Agent instance to be installed. In addition, the <global> element can be used in a homogeneous environment to specify parameters that will be applied to all Agent installations. The majority of configuration elements can be specified as <global> and as <installation> elements. If a parameter is specified in both the <global> element and in an individual <installation> element then the setting for the individual element will overwrite the global setting.

The parameters to be configured are:

Info
titlePost-processing commands
  •  Note that mandatory elements are not indicated in the XML Editor as it is possible to define a configuration items at either the globals level or at the individual agent installation level.
  • In addition, there are no default parameter settings for the batch installer. The installation will fail if mandatory configuration items are not set. Mandatory configuration items are indicated in the list of parameters below.

The parameters to be configured are:

  • The <install_path> element, which points to a location where the Agent should be installed. (Mandatory)
    the <install_path> element, which points to a location where the Agent should be installed.
  • the <transfer><settings> The <transfer><settings> element which points to the location where the YADE transfer configuration file that was configured in Section 2.1 above. (Mandatory)
    • A typical value would be C:\ProgramData\sos-berlin.com\jobscheduler\jobscheduler_1.12\config\batch_install\yade_agent_batch_installer_settings.xml
  • the The <ssh> elements (often partly configured as <global> elements):
    • <auth_method>: the authentication method to be used for the SSH connection. (Mandatory)
    • <port>: SSH port. (Mandatory)
    • <user>: SSH login account name. (Mandatory)
    • <password>: Password for the SSH login account.
    • <auth_method>: SSH authentication method. (Mandatory)
    • <host>: the host name of the target server. (Mandatory)
  • the The <installation_file> element - the name of the Universal Agent installation file. This filename contains the version of the Agent which you are installing and it is helpful for recognizing the version of the Agents that are installed. (Mandatory)
    • For Unix systems this is usually jobscheduler_unix_universal_agent.<version>.tar.gz
  • the The <agent_options> elements:
    • <java_home>: the location of the Java Runtime Environment (JRE)
      • See here for more information.
    • <java_options>: the Java options, e.g the Java memory settings
      • See here for more information
    • <scheduler_http_port>: the http port that the Universal Agent is to use.listen to. (Mandatory)
    • <scheduler_ip_address> the IP address of the target system. (Mandatory)
    • <scheduler_user>: the user name the Agent is to run under on the target system. (Mandatory)
    • <scheduler_log_dir>: the directory to be used for the Agent Log files.
    • <scheduler_kill_script> the kill scripts allows a task and it's child processes to be killed.
      • See here for more information.
    • <scheduler_pid_file_dir> the
      • See here for more information.
    • <agent_installation_script> the script to be used for the installation of the Agent (Mandatory)
      • This is usually jobscheduler_universal_agent_install.sh
  • The <postprocessing> elements:
    • The postPost-processing commands for the Agent server's operating system. The default commands for an Ubuntu distribution will place the Agent start script under /etc/init.d and will setup the autostart for the Universal Agent:
      • echo ${ssh.sudo_password} | sudo -S cp ${install_path}/jobscheduler_agent/bin/jobscheduler_agent_${agent_options.scheduler_http_port}.sh /etc/init.d/jobscheduler_agent_${agent_options.scheduler_http_port}
      • echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler_agent_${agent_options.scheduler_http_port} defaults
    • These two commands will be executed by the PerformInstall job node, which is the last job node in the batch installer job chain. If you want to add more commands, please add the call to the job node.

...