...
- First Installation: no Agent is installed and running on the server.
- Update Installation: an Agent is installed and optionally up and running.
Structure
The JobScheduler Agents will be installed from a JobScheduler Master . There is a JobScheduler job responsible for creating the Orders, which are that connects to the Agent Servers to execute the corresponding Agent installations. The structure is formed by a JobScheduler job AgentBatchInstaller
and a JobScheduler job chain universal_agent_installer
. The job AgentBatchInstaller
is responsible for creating the JobScheduler orders for the job chain. These orders are named <host>:<port>
meaning the port and the host where an Agent will be installed. The job chain have four nodes and the sequence look like this:
The job chain for update/installation of an Agent uses the nodes:
CheckPreRequisite
Sync:
To wait until all prerequisites are checked and all instances have been shut down.- Checking for the correct Java version
- Checking whether JobScheduler Universal Agent already has been installed.
- If so
- shutting down a possibly running instance
- remove the installation
- If so
Sync:
To wait until all prerequisites are checked and all instances have been shut down.
TransferInstallationSetup
: To transfer the installer files to the host- Before the transfer starts, the preprocessor will create the instance start script for the Agent instance from the templatetemplate
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 instance start script for the Agent instance from the templatetemplate
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 commands will be executed
- The postprocessing 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 setup the autostart for JobScheduler Universal Agent on a Linux server (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 commands are stored with the element
Download
The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads
...