Page History

...

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.

• 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

...

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 configuration files required for the Batch Installer. For details about the XML Editor see the Using the XML Editor chapter below.
   
   • After downloading the XML Editor, extract the contents of the zip file to a convenient folder (an installation routine is not required) and start the sos.xml.editor.exe program.
   • Open your batch_installer_config_file.xml configuration file in the XML Editor and assign the scheduler_universal_agent_installations.xsd schema: both files are located in the config/batch_installer folder.
   • Open your yade_agent_batch_installer_settings.xml YADE configurationfile, which is located in the config/batch_installer folder and assign the XSD schema http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd
2. See the Batch Installer Configuration File chapter below for instructions on how to configure the Batch Installer configuration file 
3. StatuscolourYellowtitleIntegrate 2 and 3 in 1?See the YADE profiles for the file transfer chapter below for instructions on how to configure the YADE configuration file