Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 34

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 35

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • connect to the Server(s) that the Agent(s) are to be installed on and
  • executes execute the required Agent installation(s).

...

  • CheckPreRequisite
    • Check for the correct Java version
    • Check whether a JobScheduler Universal Agent already has been installed.
      • If yes, then the Installer:
        • shuts down any instances that are possibly running
        • removes the installation
  • Sync: Wait until all prerequisites have been checked and all instances shut down.
  • TransferInstallationSetup: Transfer the installer files to the host
    • Before the transfer starts, the preprocessor will create the instance start script from the template jobscheduler_agent_instance_script.txt

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

      • This regular expression causes the following files to be transferedtransferred:
        • the JobScheduler Universal Agent installer files: jobscheduler_unix_universal_agent.<version>.tar.gz
        • the instance start script: jobscheduler_agent_<port>.sh
        • the installation script: jobscheduler_universal_agent_install.sh
  • PerformInstall: Start the installation using SSH.
    • The step before transfered transferred installation script will be executed
    • The installation script installs and starts the JobScheduler Universal Agent
    • Finally the post-processing commands will be executed
      • The post-processing commands are specified with the <installation><postprocessing><command> element
      • Three commands will be executed:
        • if you require additional commands, please add the call in the PerformInstall job
      • The default commands set up the autostart for JobScheduler Universal Agent on a Linux server (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

Installation Use Cases

The following articles describe a number of use cases regarding the installation and update of JobScheduler Agents and how to use the Agent Batch Installer solution in each casethe procedure for using the Agent Batch Installer to install and update JobScheduler Agents for a number of use cases:

Excerpt
  • Batch Installation - Use Cases - Homogeneous environment: We define a homogeneous environment as one in which a number of JobScheduler Agents will be installed according to the same prerequisites:
    • A JobScheduler Master is up and running.
    • The Agent installations are to be performed on any number of servers that have the same operating system. One Agent is to be installed per server.
    • The Agents will be operated with the same user, listening port and installation path.
  • Batch Installation - Use Cases - Heterogeneous environment: We define a heterogeneous environment as one in which a number of JobScheduler Agents will be installed according to different prerequisites:
    • A JobScheduler Master is up and running.
    • The Agent installations are to be performed on any number of servers that are not required to have the same operating system. One Agent is to be installed per server.
    • The Agents will be operated with different accounts, listening ports and installation paths.
  • Batch Installation - Use Cases - Multiple Instances: A number of JobScheduler Agents will be installed on each server and each installation will be based on different prerequisites:
    • A JobScheduler Master is up and running.
    • The Agent installations are to be performed on any number of servers that are not required to have the same operating system. More than one Agent is to be installed per server.
    • On every Agent server the Agents will be operated with different accounts and different listening ports.
      • The Agents will be operated with different accounts (within the same Agent server) to make the example more multifaceted, although the same user can operate more than one Agent if the Agents run on different ports.
    • The installation path will be the same for all Agent installations.

...

Reference Documentation

For detailed information aboutnot contained in the installation use case articles described above, covering:

  • the jobs, job parameters and job chains used for the Agent Batch Installer
  • customizing the jobs, job chains and the configuration files required for the Agent Batch Installer to work

...