Page History

Environment

We consider This article describes the use of the JobScheduler Universal Agent batch installer/updater in a homogeneous environment. We define a homogeneous environment a scenario 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 performed for an arbitrary to be performed on any number of servers with that have the same operating system. One Agent is to be installed per server.
• The Agents are will be operated with the same user, listening port and installation path.

The Batch Installer supports:

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

Operation of th Batch Installer/Updater Structure

The JobScheduler Agents will be installed from 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 a JobScheduler AgentBatchInstaller job  and a JobScheduler to execute the corresponding Agent installations. The structure is formed by a JobScheduler job AgentBatchInstaller and a JobScheduler job chain universal_agent_installerjob chain. The AgentBatchInstaller job AgentBatchInstaller is is responsible for creating the JobScheduler orders for the job chain. These Each of these orders are is named according to the pattern <host>:<port> meaning to convey the host and port and of the host server where an the respective Agent will is to be installed. 

The The universal_agent_installer job chain have has four job nodes and the sequence look like thisconfigured in series as follows:

The job chain for update/installation of an Agent uses the nodesindividual nodes in the universal_agent_installer job chain have the following functions:

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

  Status
  colour Yellow title In der Diagram ist sync ein extra Node

  • Check
  • Checking for the correct Java version.
  • Checking Check whether a JobScheduler Universal Agent has already has been installed. If so:
    • • shutting down a possibly running instanceshut down the instance if it is running,
        
      • remove the installation.

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

     

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

    Status
    colour Yellow title Does this filter <all> files?

  • This regular expression is used toWith this regular expression, the following files will be transfered:
    
    • the JobScheduler Universal Agent installer installation files: jobscheduler_unix_universal_agent.tar.gz
      the instance start script: the jobscheduler_agent_<port>.sh start script for the instance
    • the installation script: jobscheduler_universal_agent_install.sh
• PerformInstall: To start the installation using The installation is started by SSH.
  • The step before transfered installation script will be executed

    Status
    colour Yellow title WHAT IS THE NAME OF THIS SCRIPT

    
    
  • The installation script will install and start the JobScheduler Universal Agent
  • Finally Finally the PerformInstall job post-processing commands will be executed:
    • The post-processing These commands are stored with specified using the element  <installation><postprocessing><command> element.
       
    • The default commands configuration for a Linux server will place the Agent start script under /etc/init.d and will setup set up the autostart for JobScheduler Universal Agent on a Linux server (example for an 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

...

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

...

1. Configuring XML files with a text editor is error-prone. Therefore we recommend that you download the XML Editor that can be used to manage the necessary configuration files required for the Batch Installer. For details about the XML Editor see the below chapter  Using the XML Editor chapter below.
   
   • After download of After downloading the XML Editor, extract the contents of the zip file , then to a convenient folder (an installation routine is not required) and start the program sos.xml.editor.exe program.
   • Open your Batch Installer configuration file  batch_installer_config_file.xml configuration file in the XML Editor and assign the XSD schema  scheduler_universal_agent_installations.xsd, schema: both files are located in the folder config/batch_installer folder.
   • Open your YADE configuration file yadeyade_agent_batch_installer_settings.xml that xml YADE configurationfile, which is located in the folder  config/batch_installerfolder and assign the XSD schema http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd
   For instructions
2. See the Batch Installer Configuration File chapter below for instructions on how to configure the Batch Installer configuration file 

   Status
   colour Yellow title Integrate 2 and 3 in 1?

3. See the YADE profiles for the file transfer chapter below for instructions on file see the below chapter Batch Installer Configuration File. For instructions how to configure the YADE configuration file see the below chapter YADE profiles for the file transfer.



JobScheduler Jobs

• Job AgentBatchInstaller: Adjust the parameter values for the AgentBatchInstaller job in your JobScheduler Master.

  • Adjust the installation_definition_file job parameter with the path that points to the Batch Installer configuration file.

...