...
- First Installation: an Agent has not yet been installed on the server.
- Update Installation: an Agent has already been installed and may be up and running.
Excerpt |
---|
Anchor |
---|
| batch_installer_app |
---|
| batch_installer_app |
---|
| The Batch Installer ApplicationThe Batch Installer is operated by a JobScheduler Master that: - connects to the Servers that the Agents are to be installed on and
- executes the required Agent installations.
The Batch Installer application has two main components: - a JobScheduler
AgentBatchInstaller job and - a JobScheduler
universal_agent_installer job chain.
In addition, two XML files are needed for the application: batch_installer_config_file.xml and yade_agent_batch_installer_settings.xml
The AgentBatchInstaller job is responsible for creating the JobScheduler orders for the job chain. Each of these orders is named according to the pattern <host>:<port> to convey the host and port of the server where each Agent is to be installed. The universal_agent_installer job chain has four job nodes configured in series as follows: Image Added
The individual nodes in the job chain have the following functions: CheckPreRequisite - Check for the correct Java version
- Check whether a JobScheduler Universal Agent already has been installed.
- If yes, then the Installer:
- shuts down any instances that are possibly running
- removes the installation
Sync: Wait until all prerequisites have been checked and all instances shut down.TransferInstallationSetup : Transfer the installer files to the host
PerformInstall : Start the installation using SSH.- The step before transfered installation script will be executed
- The installation script installs and starts the JobScheduler Universal Agent
- Finally the post-processing commands will be executed
- The post-processing commands are specified with the
<installation><postprocessing><command> element
- Three commands will be executed:
- if you require additional commands, please add the call in the
PerformInstall job
- The default commands set up 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
Download the Batch Installer and Agent FilesThe following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads - Unix
- Download the "JobScheduler Universal Agent" tarball for Unix.
- Download the "Universal Agent Batch Installer". The archive contains the following:
- a
config/live/batch_installer_agent folder, with the jobs and job chains. Extract these files to the the live folder of the JobScheduler Master: SCHEDULER_DATA/config/live . - a
config/batch_installer folder with the configuration files for the Batch Installer. Extract these files to the config directory of the JobScheduler Master: SCHEDULER_DATA /config . - Copy the JobScheduler Universal Agent installation file to the
SCHEDULER_DATA/config/ batch_installer folder.
- Windows
- Download the "JobScheduler Universal Agent" for Windows.
- Download the "Universal Agent Batch Installer". The archive contains the following
- the
config/live/batch_installer_agent folder with the jobs and job chains. Extract these files to the live folder of the JobScheduler Master SCHEDULER_DATA/config/live . - the
config/batch_installer folder with the configuration files for the Batch Installer. Extract these files to the JobScheduler configuration directory SCHEDULER_DATA/config . - Copy the JobScheduler Universal Agent installation file to the folder
SCHEDULER_DATA/config/ batch_installer .
|
Excerpt Include |
---|
Batch Installation - Use Cases - Heterogeneous environment | Batch Installation - Use Cases - Heterogeneous environment | nopanel | trueConfiguration
XML files
Configuring complex XML files with a text editor is often a tedious and error-prone procedure. To get around this, we recommend that you use our XML Editor to manage the configuration files required for the Batch Installer. The XML Editor automatically validates configuration files and therefore reduces the possibility of configuration errors. See the Using the XML Editor chapter below for more detailed information about using the XML Editor.
...