Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: 'Batch Installer Application' Extract updated

...

  • 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 Application

The JobScheduler Agents will be installed 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
  •  job and
  • a JobScheduler universal_agent_installer job chain.

In addition, two XML files files are needed for the application:

  • 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 the job chain have the following functions:

  • CheckPreRequisite
    • Check Checks for the correct Java version.
    • Check Checks whether a JobScheduler Universal Agent has already been already has been installed.
      • If so:
        • shut down the instance if it is running,
        • shuts down any instances that are possibly running
        • removes the installationremove the installation.
  • Sync:  To wait Waits until all prerequisites have been checked and any already installed Agent instances that are running have been all instances shut down.
  • TransferInstallationSetup: To transfer Transfers the installer files on to the host
    • Before the transfer starts, the preprocessor will use the use the create the instance start script from the template 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.
    • txt
    • The files that are to The files that will be transfered are specified with the element  <globals><transfer><file_spec=".*\.(sh|gz)$">  configuration element

      • This regular expression
      is used to select
      • causes the following files to be transfered:
        • the JobScheduler Universal Agent
        installation
        • installer files:
         
        • jobscheduler_unix_universal_agent.<version>.tar.gz

        the 
        • the instance start script: jobscheduler_agent_<port>.sh
         start script for the instance
        • the installation script:
         
        • jobscheduler_universal_agent_install.sh
  • PerformInstall: The installation is started by Starts the installation using SSH.
    • The step before transfered installation script will be executed
    • The installation script installs and starts install and start the JobScheduler Universal Agent
    • The PerformInstall job postFinally the post-processing commands will then be executed:
      • These The post-processing commands are specified using the <installation><postprocessing><command> element.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 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 on a Linux server (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. Unix
    • Download the "JobScheduler Universal Agent" tarball for Unix.
    • Download the "JobScheduler Universal Agent Batch Installer" for Unix. The archive contains the following: 
      • 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.
      • 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.
  2. Windows
    • Download the "JobScheduler Universal Agent" for Windows.
    • Download the "JobScheduler Universal Agent Batch Installer" for Windows. 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.

...