Page History

...

This article describes the use of the JobScheduler Universal Agent batch installer/updater 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:

...

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

Operation of

...

the Batch Installer

...

Structure

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 Installer / Updater structure is made up of Batch Installer application has two main components - a JobScheduler AgentBatchInstaller job  and a JobScheduler universal_agent_installer job chain. 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 individual nodes in the universal_agent_installer job chain have the following functions:

• CheckPreRequisiteSync: To wait until all prerequisites have been checked and any already installed Agent instances that are running have been shut down.

  Show If
  group sos-members
  Status colour Yellow title In der Diagram ist sync ein extra Node

   
  • 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 files that are to be transfered are specified with the element <globals><transfer><file_spec=".*\.(sh|gz)$">

    Show If
    group sos-members
    Status colour Yellow title Does this filter <all> files?

  • This regular expression is used to, the following files will 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 step before transfered installation script will be executed
    

    Show If
    group sos-members
    Status colour Yellow title WHAT IS THE NAME OF THIS SCRIPT

  • 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

...

...