...
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 configuration 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.1.11.0-SNAPSHOT.tar.gz
- the instance start script:
jobscheduler_agent_<port>.sh
- the installation script:
jobscheduler_universal_agent_install.sh
- the JobScheduler Universal Agent installer files:
- Before the transfer starts, the preprocessor will create the start script for the Agent instance from the template
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 postprocessing post-processing commands will be executed
- The postprocessing post-processing commands are stored with the element
<installation><postprocessing><command>
- Three commands will be executed
- if you have more than three commands, please add the call in the job
PerformInstall
- if you have more than three commands, please add the call in the job
- 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}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler
echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defaults
- The postprocessing post-processing commands are stored with the element
...
- 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 forsudo
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: - specify the command for copying a file (e.g. for CentOS:
cp
) specify the command for setting the auto-start for the Agent (e.g. for CentOS: echo ${ssh.sudo_password} | sudo -S cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler
echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defaults
chkconfig
). 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): - Specify the
- Installation parameters (specified for each Agent installation):
- Agent options:
<scheduler_user>
: Agent user<scheduler_log_dir>
: Logs folder for the Agent
- SSH Host
- Agent options:
Info | ||
---|---|---|
| ||
...