Page History

...

The JobScheduler Agents will be installed from a JobScheduler Master that connects to the Agent Servers to execute the corresponding Agent installations. The structure is formed by a JobScheduler job AgentBatchInstaller and a JobScheduler job chain universal_agent_installer. The job AgentBatchInstaller is responsible for creating the JobScheduler orders for the job chain. These orders are named <host>:<port> meaning the port and the host where an Agent will be installed. 

The job chain have four job nodes and the sequence look like this:

...

• CheckPreRequisiteSync: To wait until all prerequisites are checked and all instances have been shut down.
  • Checking for the correct Java version
  • Checking whether JobScheduler Universal Agent already has been installed.  
    If so:
    • • shutting down a possibly running instance
      • remove the installation

• TransferInstallationSetup: To transfer the installer files to the host
  • Before the transfer starts, the preprocessor will create the start script for the Agent instance from the template jobscheduler_agent_instance_script.txt

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

  • With this regular expression, the following files will be transfered:
    
    • the JobScheduler Universal Agent installer files: jobscheduler_unix_universal_agent.tar.gz
    • the instance start script: jobscheduler_agent_<port>.sh
    • the installation script: jobscheduler_universal_agent_install.sh
• PerformInstall: To start the installation using SSH.
  • The step before transfered installation script will be executed
  • The installation script will install and start the JobScheduler Universal Agent
  • Finally the post-processing commands will be executed
    • The post-processing commands are stored with the element <installation><postprocessing><command>
    • Three commands will be executed 
      
      • if you have more than three commands, please add the call in the job PerformInstall
    • The default commands will place the Agent start script under /etc/init.d and will setup the autostart for JobScheduler Universal Agent on a Linux server (example for an 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

...

1. Unix
   • Download the "JobScheduler Universal Agent" tarball for Unix.
   • Download the "JobScheduler Universal Agent Batch Installer" for Unix. 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 config directory of the JobScheduler Master ${SCHEDULER_DATA}/config.
     • Copy the JobScheduler Universal Agent installation file to the folder ${SCHEDULER_DATA}/config/batch_installer.
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.

...