Page History

...

• 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 Include
Batch Installer - Use Cases - Heterogeneous environment Batch Installer - Use Cases - Heterogeneous environment nopanel true

...

The JobScheduler Agents will be installed 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 batch_installer_config_file.xml and yade_agent_batch_installer_settings.xml are needed for the application. 

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:

...

The individual nodes in the universal_agent_installer job chain have the following functions:

• CheckPreRequisite

  • Check for the correct Java version.
  • Check whether a JobScheduler Universal Agent has already been installed. If so:
    • • shut down the instance if it is running,
        
      • remove the installation.
• Sync: To wait until all prerequisites have been checked and any already installed Agent instances that are running have been shut down.
  

• TransferInstallationSetup: To transfer the installer files on the host
  • Before the transfer starts, the preprocessor will use the use the jobscheduler_agent_instance_script.txt template to create a start script for each Agent instance. 
  • The XML file yade_agent_batch_installer_settings.xml has to be configured and converted to .ini file before the transfer starts. See the YADE configuration file for the file transfer chapter below for instructions on how to configure the YADE configuration file and YADE Settings File for the File Transfer for instructions on how the .ini file should look like.

  • The files that will be transfered are specified with the element <globals><transfer><file_spec=".*\.(sh|gz)$">  

  • This regular expression is used to select the files to be transfered:
    
    • the JobScheduler Universal Agent installation files: jobscheduler_unix_universal_agent.tar.gz
      the jobscheduler_agent_<port>.sh start script for the instance
    • the installation script: jobscheduler_universal_agent_install.sh
• PerformInstall: The installation is started by SSH.
  • The installation script will install and start the JobScheduler Universal Agent
  • The PerformInstall job post-processing commands will then be executed:
    • These commands are specified using the <installation><postprocessing><command> element.
    • The default configuration for a Linux server will place the Agent start script under /etc/init.d and set up the autostart for JobScheduler Universal Agent (the following example is for a 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

...

• Download the "JobScheduler Universal Agent" tarball for Unix.
• Download the "JobScheduler Universal Agent Batch Installer" for Unix. The archive contains the following: 
  • a 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.
  • a config/batch_installer folder containing 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.
    

...

Configuration

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. 

...