Page History

...

• A JobScheduler Master is up and running.
• A number of JobScheduler Agents have already been installed on different Agent servers.
  • At least one additional Agent is to be installed operated on a server which already has an Agent installed on it.
• The new Agent(s) will be operated with the same user and installation path as at least one of the Agents already installed on an Agent server.
  The new Agent will be identified by its listening port which will be unique for the server which the Agent is being installed on.

...

The JobScheduler Agents will be installed by the JobScheduler Master which:

• connects to the Servers servers that the Agents are to be installed on and
• executes the required Agent installations.

The 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 uses a name according to the pattern <host>:<port> to convey the host and port of the server where each Agent is to be installed.

...

Carry out the following once the job and job chain have been extracted to the live folder of your the JobScheduler Master: 

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

  • Set the installation_definition_file job parameter to the path to the Batch Installer configuration file.

  • Set the update job parameter to false. This will ensure that in the example described below the Batch Installer will not attempt to update existing Agent installations that have been installed using the Batch Installer - and whose configurations are included in the Batch Installer Configuration File.

...

The following configuration steps would need to be carried out to add the configuration for the additional agent Agent to this file:

1. Leave the global parameters as they were set for your previous Use Case.
2. Specify the installation parameters for the extra Agent installation:
   • Set lastRun attribute to an empty value (for the <installations><installation> element). This is the value that will make the Batch Installer just carry out this one additional installation and skip (i.e. not attempt to update) the rest.
   • Agent options:
     • <scheduler_user>: the Agent user
     • <scheduler_log_dir>: the Logs folder for the Agent

   • Specify the credentials for the SSH connection:

     • <user>: the SSH login user 
     • <password>: the Password for the login user
     • <sudo_password>: the Password for sudo actions
     • <auth_method>: the SSH authentication method
     • <host>: the SSH Host
     • <port>: the SSH port 
   • Use the <postprocessing> element to specify the post-processing commands for the Agent server's operating system. The default commands for an Ubuntu distribution will place the Agent start script under /etc/init.d and will setup the autostart for the Universal Agent:
     

     • 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

...