Scenarios

We define an homogeneous environment as an environment where the Agents that want to be installed are going to be installed under the same conditions. We only differentiate here between a fresh installation and an update from an already installed Agent.

Scenario 1: Fresh installation and same conditions in each Agent server

Let be the following scenario:

• One JobScheduler Master is running.
• N different servers, where ONE JobScheduler Universal Agent instance has to be installed (Agent server). 
• The ports where the JobScheduler Universal Agents will be running are the same ones.
• The users, which the JobScheduler Universal Agents is running under, are named the same.
• There has been no previous JobScheduler Universal Agents installations on these N servers.

Installation Steps

....

Example

The Installer Configuration File

The installer configuration file contains an <installation> element for each JobScheduler Universal Agent instance.

A minimal example for the installer configuration file can look like this:

 <?xml version="1.0" encoding="utf-8"?>
<installations lastRun="2015-11-06 15:11">
  <globals>
    <transfer>
      <settings><![CDATA[C:\Temp\batch_install\yade_agent_batch_installer_settings.ini]]></settings>
    </transfer>
  </globals>
  <installation lastRun="2015-11-06 15:11">
    <install_path><![CDATA[/home/test/temp/xxx]]></install_path>
    <agent_options>
      <scheduler_http_port>4445</scheduler_http_port>
      <scheduler_ip_address><![CDATA[192.11.0.116]]></scheduler_ip_address>
    </agent_options>
    <ssh>
      <user><![CDATA[test]]></user>
      <password><![CDATA[12345]]></password>
      <sudo_password><![CDATA[12345]]></sudo_password>
      <auth_method><![CDATA[password]]></auth_method>
      <port><![CDATA[22]]></port>
    </ssh>
    <postprocessing>
      <command><![CDATA[echo ${ssh.sudo_password} | sudo -S cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler]]></command>
      <command><![CDATA[echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defaults]]></command>
    </postprocessing>
  </installation>
</installations>

With the <globals> element you specify the values that are used for all installation items. The items that are specific for an individual installation will overwrite the global values. There is one installation item for each Agent. You can use substitution in the values of the elements.

<command>echo ${ssh.sudo_password} | sudo cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler</command>

Scenario 2

Let be the following scenario:

• One JobScheduler Master is running.
• N different servers, where ONE JobScheduler Universal Agent instance has to be installed. 
• The ports where the JobScheduler Universal Agents will be running are the same ones 
• The users, which the JobScheduler Universal Agents is running under are named the same.
• It is NOT a fresh installation, instead it is an update of the JobScheduler Universal Agents that have been already installed on the servers.

Installation

..

Example

...