Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • TransferInstallationSetup: To transfer the installer files to the host
    • Before the transfer starts, the preprocessor will create the start script for the Agent instance from the template jobscheduler_agent_instance_script.txt
    • The files that will be transfered are specified with the element <globals><transfer><file_spec=".*\.(sh|gz)$">

    • With this regular expression, the following files will be transfered:
      • the JobScheduler Universal Agent installer files: jobscheduler_unix_universal_agent.tar.gz
      • the instance start script: jobscheduler_agent_<port>.sh
      • the installation script: jobscheduler_universal_agent_install.sh
  • PerformInstall: To start the installation using SSH.
    • The step before transfered installation script will be executed
    • The installation script will install and start the JobScheduler Universal Agent
    • Finally the post-processing commands will be executed
      • The post-processing commands are stored with the element <installation><postprocessing><command>
      • The default commands will place the Agent start script under /etc/init.d and will setup the autostart for JobScheduler Universal Agent on a Linux server (example for an Ubuntu distribution):
        • 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

Download

The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads

...

  1. Global parameters:
    • Specify the <install_path> to point to a location where the Agent should be installed.
    • Specify the path to the YADE settings file (.ini file) in the Batch Installer configuration file with the element <globals><transfer><settings>.
    • Specify the credentials for the SSH connection:
      • <user>: SSH login user 
      • <password>: Password for the login user
      • <sudo_password>: Password for sudo actions
      • <auth_method>: SSH authentication method
      • <port>: SSH port 
    • Specify the post-processing commands that fit your operating system on the Agent server with the <postprocessing> element. The default commands will place the Agent start script under /etc/init.d and will setup the autostart for JobScheduler Universal Agent on a Linux server (example for an Ubuntu distribution):
      • echo ${ssh.sudo_password} | sudo -S cp ${install_path}/jobscheduler_agent/bin/jobscheduler_agent
        .sh /etc
        _${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
  2. Installation parameters (specified for each Agent installation):
    • Agent options:
      • <scheduler_user>: Agent user
      • <scheduler_log_dir>: Logs folder for the Agent
    • SSH Host 

Info
titlePost-processing commands
  • The SSH login user has to become root in order to execute these commands. Therefore the SSH login user should be included to sudoers.
  • These two commands will be executed by the job node PerformInstall, the last job node in the job chain. If you want to add more commands, please add the call on the job node.
  • Note that the values for the elements defined in the Batch Installer configuration file can be used for the postprocessing commands, for instance:
    • ${install_path}: the value for the element <install_path>

    • ${agent_options.scheduler_http_port}: the value for the element <scheduler_http_port>. If not defined, the default value (4445 in this case) is taken, like in the example below.

 

An example for the Batch Installer configuration file for the installation of two Agents might look like this:

Code Block
languagexml
titleBatch Installer Configuration File
collapsetrue
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installations lastRun="2015-11-20 14:11">
    <globals>
        <install_path>/opt</install_path>
        <transfer>
            <settings>C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer\yade_agent_batch_installer_settings.ini</settings>
        </transfer>
        <ssh>
			<user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <auth_method>password</auth_method>
            <port>22</port>
        </ssh>
        <postprocessing>
            <command>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}</command>
            <command>echo ${ssh.sudo_password} | sudo -S chkconfigupdate-rc.d jobscheduler_agent_${agent_options.scheduler_http_port}< defaults</command>
        </postprocessing>
    </globals>
    <installation lastRun="2015-11-20 14:11">
        <agent_options>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <host>xxxx</host>
        </ssh>
    </installation>
    <installation lastRun="2015-11-20 14:11">
        <agent_options>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <host>xxxx</host>
        </ssh>
    </installation>
</installations>

...