Scenarios

Scenario 1

Let be the following scenario:

• One JobScheduler Master is running.
• N different servers, where K JobScheduler Universal Agent instances have to be installed on each server. 
• The ports where the JobScheduler Universal Agents will be running are the NOT the same ones, by what is meant within the ports taken for the same server, in case more than one instance will be installed on the same Agent Server.
• The users, which the JobScheduler Universal Agents is running under are NOT named the same.
• There has been no previous JobScheduler Universal Agents installations on the N servers.

Scenario 2

Let be the following scenario:

...

Environment

This article describes the use of the JobScheduler Universal Agent Batch Installer in a homogeneous environment. We define a homogeneous environment as one in which a number of JobScheduler Agents will be installed based on the same prerequisites:

• A JobScheduler Master is up and running.
• The Agent installations are to be performed on any number of servers that do not have to have the same operating system. More than one Agent is to be installed per server.
• In every Agent server, the Agents will be operated with different users and different listening ports.
• The installation path will be the same for all Agent installations.

The Batch Installer supports:

• First Installation: an Agent has not yet been installed on the server.
• Update Installation: an Agent has already been installed and optionally up and running.

Anchor
batch_installer_app batch_installer_app

Batch Installer Application

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 corresponding Agent installations.

The Batch Installer application has two main components - a JobScheduler AgentBatchInstaller job  and a JobScheduler universal_agent_installer job chain. Moreover, 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 the respective 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 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 to 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 the 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 the following 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
  • Finally the PerformInstall job post-processing commands will 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(example 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

1. Unix
   • 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 that are to be extracted to the live folder of the JobScheduler Master: SCHEDULER_DATA/config/live.
     • a config/batch_installer folder containing configuration files for the Batch Installer. These files should be extracted 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 provides the following content:
     • the config/live/batch_installer_agent folder contains jobs and job chains that should be extracted to the live folder of the JobScheduler Master SCHEDULER_DATA/config/live.
     • the config/batch_installer folder contains configuration files for the Batch Installer that should be extracted to the JobScheduler configuration directory SCHEDULER_DATA/config.
     • Copy the JobScheduler Universal Agent installation file to the folder SCHEDULER_DATA/config/batch_installer.

Installation and Configuration Steps

...