Page History

Table of Contents

...

Introduction

This article describes the use of is one of a series describing how to configure the JobScheduler Universal Agent Batch Installer in a homogeneous environment. We define a homogeneous environment as one in which so that a number of JobScheduler Universal Agents will can be readily installed based on the same prerequisites:

A JobScheduler Master is up and running.
The Agent installations are to be performed on any number of servers that do not have to have the same operating system. More than one Agent is to be installed per server.
In every Agent server, the Agents will be operated with different users and different listening ports.
The installation path will be the same for all Agent installations.

The Batch Installer supports:

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

...

on a number of servers.

Article Scope

This article describes how to use the Universal Agent Batch Installer to install multiple Agent instances. Other use cases in this series of articles are listed in the introductory JobScheduler Universal Agent - Batch Installation and Update of Agents article.

A general introduction to installation of the JobScheduler Universal Agent can be found in the JobScheduler Universal Agent - Installation & Operation article.

The JobScheduler Universal Agent - Batch Installation and Update of Agents article provides an overview of how the Batch Installer works. New users are strongly recommended to read this article before proceeding with the instructions presented here.

The Batch Installation - Reference Documentation article provides a detailed guide to configuration of the batch installer with, for example, full lists of parameters.

Installation Environment

This article describes the use of the JobScheduler Universal Agent Batch Installer for installing multiple Agent instances in a heterogeneous environment. A number of JobScheduler Agents will be installed on every Agent server and every 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 do not have to have the same operating system. More than one Agent is to be installed per server.
In every Agent server, the Agents will be operated with different users and different listening ports.
- The Agents will be operated with different users (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

Installation Procedure

General requirements:

A JobScheduler Master is up and running.
A Java Run-time Environment in version 1.8 or newer is installed on the system(s) the Agent is to be installed on.
We recommend that you use the SOS XML Editor to manage the configuration files required for the Batch Installer. More information about the installation and use of the XML editor will be provided later in this article.

1. Download and Extract the Batch Installer and Agent Files

...

The JobScheduler Agents will be installed by a JobScheduler Master that:

connects to the Servers that the Agents are to be installed on and
executes the corresponding Agent installations.

The Batch Installer application has two main components - a JobScheduler AgentBatchInstaller job and a JobScheduler universal_agent_installer job chain. Moreover, two XML files batch_installer_config_file.xml and yade_agent_batch_installer_settings.xml are needed for the application.

The AgentBatchInstaller job is responsible for creating the JobScheduler orders for the job chain. Each of these orders is named according to the pattern <host>:<port> to convey the host and port of the server where the respective Agent is to be installed.

The universal_agent_installer job chain has four job nodes configured in series as follows:

...

The individual nodes in the universal_agent_installer job chain have the following functions:

CheckPreRequisite
- 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.
Sync: To wait until all prerequisites have been checked and any already installed Agent instances that are running have been shut down.

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 XML file yade_agent_batch_installer_settings.xml has to be configured and converted to .ini file before the transfer starts. See the YADE configuration file for the file transfer chapter below for instructions on how to configure the YADE configuration file and YADE Settings File for the File Transfer for instructions on how the .ini file should look like.
- The files that will be transfered are specified with the element <globals><transfer><file_spec=".*\.(sh|gz)$">
- This regular expression is used to the following files to 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 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

...

The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads
1.1 Unix
Download the "JobScheduler Universal Agent" tarball for Unix.
Download the "JobScheduler Universal Agent Batch Installer" for Unix. The The archive contains the following folders and sub-folders:
a `config/live/batch_install_installeruniversal_agent` folder, with the jobs and job chains that are to be extracted to
This folder contains the Jobs and Job Chain used to carry out the installation.
Extract these files to the the `live` folder of the JobScheduler Master: `SCHEDULER_DATA/config/live`.
a `config/batch_installer` folder containing configuration `install`
This folder contains the configuration files for the Batch Installer.
These files should be extracted
Extract these files to the `config` directory of the JobScheduler Master: `SCHEDULER_DATA/config`.
Copy the JobScheduler Universal Agent installation file to the `SCHEDULER_DATA/config/batch_`installer folder`install` folder.
1.2 Windows
Download the "JobScheduler Universal Agent" for Windows.
Download the "
...
Universal Agent Batch Installer"
...
. The archive
...
contains the following
...
folders and sub-folders
the
`live/batch_install_`
...
`universal_agent` folder
This folder contains
...
the Jobs and Job Chain used to carry out the installation.
Extract these files to the `live` folder of the JobScheduler Master `SCHEDULER_DATA/config/live`.
...
the `batch_`
...
`install` folder
This folder contains the configuration files for the Batch Installer
...
.
Extract these files to the JobScheduler configuration directory `SCHEDULER_DATA/config`.
Copy the JobScheduler Universal Agent installation file to
...
the folder `SCHEDULER_DATA/config/batch_install` folder`.`

2. Configure the Transfer of the Universal Agent Installation Files and the Installation of the Agents

2.1 Edit the XML Configuration files

Configuring complex

Configuration

XML files

Configuring XML files with a text editor is often a tedious and error-prone procedure. Therefore To get around this, we recommend that you download the you use our XML Editor that can be used to manage the configuration files required for the Batch Installer. For details about the XML Editor see The XML Editor automatically validates configuration files and therefore reduces the possibility of configuration errors. See the Using the XML Editor chapter below for more detailed information about using the XML Editor.

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 the sos.xml.editor.exe program program.
Use the XML Editor to configure transfer of the Universal Agent installation files:
Open your
- Open your
- yade_agent_batch_installer_settings.xml
YADE
- YADE configuration
- file, which is located in
the the config/batch_installer folder folder and assign the XSD following schema in the XML Editor:http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd. See See the YADE profiles for the file transfer chapter below for instructions on how to configure the YADE configuration file.
Use the XML Editor to configure the installation of the Universal Agents: 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. See See the Batch Installer Configuration File chapter below for instructions on how to configure the Batch Installer configuration file.

Info

title	Hints

The XML Editor is available for Windows.
YADE is an Open Source file transfer solution for FTP, SFTP, FTPS, WebDAV and other protocols. Concretely, it will be used here for transferring the following files from the JobScheduler Master to the Agent servers:
- JobScheduler Universal Agent installation files: jobscheduler_unix_universal_agent.1.11.0-SNAPSHOT<version>.tar.gz
- Start script for an Agent instance: jobscheduler_agent_<port>.sh
- Installation script: jobscheduler_universal_agent_install.sh
For more information about YADE, see the YADE product site.

`2.2 Configure the JobScheduler Jobs`

Once the job and job chain were Job and Job Chain have been extracted to the the live folder folder of your JobScheduler Master , please do carry out the following:

AgentBatchInstaller Job: Set AgentBatchInstaller job: adjust the parameter values for the AgentBatchInstaller job in your JobScheduler Master. Adjust Set the installation_definition_file job parameter with to the path that points to the Batch Installer configuration file.

`3 Installation of the Agents`

The Agents can be installed after the XML configuration files and JobScheduler jobs Jobs have been configured. Start a task for the AgentBatchInstaller AgentBatchInstaller job as follows:

Open a JobScheduler Operating Center (JOC) browser window for the JobScheduler masterwindow for the JobScheduler master.
Go on the "Jobs" Window and open the "batch_installer_universal_agent" folder.
Right click on the job to open the context menu.
Select the Start task immediately operation operation.
This job will create the appropriate Orders for the JobScheduler

 orders  as explained in the description of the 
 chapter  Batch Installer Application.

`Example: Installation of four Agents on two Servers`

The following example describes how to do the installation of install four JobScheduler Universal Agents in on two Agent Servers , - that is, two JobScheduler Universal Agents will be installed per server. First of all, the YADE configuration files (XML file ) for the file transfer will be specified, then configured (in XML format), it will then be converted to the YADE settings file format (.ini) and finally the Batch Installer configuration file will be specified.

Anchor
yade_profile_transfer
yade_profile_transfer
`YADE`

...

`Configuration File for File Transfer`

We assume that you have opened the yade_agent_batch_installer_settings.xml YADE configuration file and have assigned the http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd XSD schema. The XML file contains a basic example with recommended values for an Agent the installation ( of only one a single Agent).

A separate profile in the YADE configuration file is required for each Agent installation. The default profile name is <host>:<port> where:

<host> will be substituted with the value from the element <installation><agent_option><scheduler_ip_address>
<port> will be substituted with the value from the element <installation><agent_option><scheduler_http_port>

Please take Now carry out the following steps:

Add a <ProtocolFragments> element and nodes for each host that you want to install the Agent for. The best way to add another <ProtocolFragments> element using the XML Editor is copying the element and pasting it to the parent element - in this case <Fragments>.
Add a <Profile> element and nodes for each host that you want to install the Agent for. The best way to add another <Profile> element using the XML Editor is copying the element and pasting it to the parent element - here <Profiles>.
The default profile_id is <host>:<port>. If you do not use the default then you have to specify the profile name in the Batch Installer configuration file.

An example for the Batch Installer The YADE configuration file for the installation of two Agents is attached on this wiki page (downloadexample can be downloaded here: yade_agent_batch_installer_settings.xml) and might look like this and is shown in the following code block:

Code Block

language	xml
title	YADE ProfilesConfiguration File
collapse	true

 <<?xml version="1.0" encoding="utf-8"?>
<Configurations xsi:noNamespaceSchemaLocation="http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <Fragments>
    <ProtocolFragments>
      <SFTPFragment name="SFTP_192.11.0.111:4445">
        <BasicConnection>
          <Hostname><![CDATA[192.11.0.111]]></Hostname>
        </BasicConnection>
        <SSHAuthentication>
          <Account><![CDATA[test]]></Account>
          <AuthenticationMethodPassword>
            <Password><![CDATA[xxxx]]></Password>
          </AuthenticationMethodPassword>
        </SSHAuthentication>
      </SFTPFragment>
      <SFTPFragment name="SFTP_192.11.0.111:4446">
        <BasicConnection>
          <Hostname><![CDATA[192.11.0.111]]></Hostname>
        </BasicConnection>
        <SSHAuthentication>
          <Account><![CDATA[sos]]></Account>
          <AuthenticationMethodPassword>
            <Password><![CDATA[xxxx]]></Password>
          </AuthenticationMethodPassword>
        </SSHAuthentication>
      </SFTPFragment>
      <SFTPFragment name="SFTP_192.11.0.95:4445">
        <BasicConnection>
          <Hostname><![CDATA[192.11.0.95]]></Hostname>
        </BasicConnection>
        <SSHAuthentication>
          <Account><![CDATA[sos]]></Account>
          <AuthenticationMethodPassword>
            <Password><![CDATA[xxxx]]></Password>
          </AuthenticationMethodPassword>
        </SSHAuthentication>
      </SFTPFragment>
      <SFTPFragment name="SFTP_192.11.0.95:4446">
        <BasicConnection>
          <Hostname><![CDATA[192.11.0.95]]></Hostname>
        </BasicConnection>
        <SSHAuthentication>
          <Account><![CDATA[test]]></Account>
          <AuthenticationMethodPassword>
            <Password><![CDATA[xxxx]]></Password>
          </AuthenticationMethodPassword>
        </SSHAuthentication>
      </SFTPFragment>
    </ProtocolFragments>
  </Fragments>
  <Profiles>
    <Profile profile_id="192.11.0.111:4445">
      <Operation>
        <Copy>
          <CopySource>
            <CopySourceFragmentRef>
              <LocalSource />
            </CopySourceFragmentRef>
            <SourceFileOptions>
              <Selection>
                <FileSpecSelection>
                  <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec>
                  <Directory><![CDATA[C:\tmp\agent_batch\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory>
                </FileSpecSelection>
              </Selection>
            </SourceFileOptions>
          </CopySource>
          <CopyTarget>
            <CopyTargetFragmentRef>
              <SFTPFragmentRef ref="SFTP_192.11.0.111:4445" />
            </CopyTargetFragmentRef>
            <Directory><![CDATA[/home/test/tmp/]]></Directory>
          </CopyTarget>
        </Copy>
      </Operation>
    </Profile>
    <Profile profile_id="192.11.0.111:4446">
      <Operation>
        <Copy>
          <CopySource>
            <CopySourceFragmentRef>
              <LocalSource />
            </CopySourceFragmentRef>
            <SourceFileOptions>
              <Selection>
                <FileSpecSelection>
                  <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec>
                  <Directory><![CDATA[C:\tmp\agent_batch\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory>
                </FileSpecSelection>
              </Selection>
            </SourceFileOptions>
          </CopySource>
          <CopyTarget>
            <CopyTargetFragmentRef>
              <SFTPFragmentRef ref="SFTP_192.11.0.111:4446" />
            </CopyTargetFragmentRef>
            <Directory><![CDATA[/home/sos/tmp/]]></Directory>
          </CopyTarget>
        </Copy>
      </Operation>
    </Profile>
    <Profile profile_id="192.11.0.95:4445">
      <Operation>
        <Copy>
          <CopySource>
            <CopySourceFragmentRef>
              <LocalSource />
            </CopySourceFragmentRef>
            <SourceFileOptions>
              <Selection>
                <FileSpecSelection>
                  <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec>
                  <Directory><![CDATA[C:\tmp\agent_batch[CDATA[C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory>
                </FileSpecSelection>
              </Selection>
            </SourceFileOptions>
          </CopySource>
          <CopyTarget>
            <CopyTargetFragmentRef>
              <SFTPFragmentRef ref="SFTP_192.11.0.95:4445" />
            </CopyTargetFragmentRef>
            <Directory><![CDATA[/home/sos/tmp/]]></Directory>
          </CopyTarget>
        </Copy>
      </Operation>
    </Profile>
    <Profile profile_id="192.11.0.95:4446">
      <Operation>
        <Copy>
          <CopySource>
            <CopySourceFragmentRef>
              <LocalSource />
            </CopySourceFragmentRef>
            <SourceFileOptions>
              <Selection>
                <FileSpecSelection>
                  <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec>
                  <Directory><![CDATA[C:\tmp\agent_batch\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory>
                </FileSpecSelection>
              </Selection>
            </SourceFileOptions>
          </CopySource>
          <CopyTarget>
            <CopyTargetFragmentRef>
              <SFTPFragmentRef ref="SFTP_192.11.0.95:4446" />
            </CopyTargetFragmentRef>
            <Directory><![CDATA[/home/test/tmp/]]></Directory>
          </CopyTarget>
        </Copy>
      </Operation>
    </Profile>
  </Profiles>
</Configurations>Configurations>

Anchor
yade_settings_file
yade_settings_file
`YADE Settings File for File Transfer`

Note that the file shown above is an in the YADE XML file format and that YADE versions less that 1.11 10 and older require a .ini file to perform the transfer that is specified in the <globals><install_path><transfer><settings> element in the Batch Installer configuration file.

We recommended that you use the XML Editor to convert configuration files from XML to the .ini format (see the XML Editor for converting YADE configuration files (XML) into YADE setting files (.ini) section below for more information).
The following example shows as an example a .ini file that has been converted from the XML file above. You can download the example here example using this link: yade_agent_batch_installer_settings.ini.

...

Code Block

title	INI .ini file
collapse	true

[protocol_fragment_sftp@SFTP_192.11.0.111:4445]
protocol                            = sftp
host                                = 192.11.0.111
user                                = test
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.111:4446]
protocol                            = sftp
host                                = 192.11.0.111
user                                = sos
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.95:4445]
protocol                            = sftp
host                                = 192.11.0.95
user                                = sos
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.95:4446]
protocol                            = sftp
host                                = 192.11.0.95
user                                = test
ssh_auth_method                     = password
password                            = xxxx
[192.11.0.111:4445]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                             = C:\tmp\agent_batch= C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.111:4445
target_dir                          = /home/test/tmp/
[192.11.0.111:4446]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.111:4446
target_dir                          = /home/sos/tmp/
[192.11.0.95:4445]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.95:4445
target_dir                          = /home/sos/tmp/
[192.11.0.95:4446]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                            = C:\tmp\agent_batch= C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.95:4446
target_dir                          = /home/test/tmp/

Anchor
installer_config_file
installer_config_file
`Batch Installer Configuration File`

We assume that you you have opened the Batch Installer configuration file batch_installer_config_file.xml xml in the XML Editor and assigned the scheduler_universal_agent_installations.xsd XSD schema. The XML file contains a basic example with recommended values for an Agent installation.

The Batch Installer configuration file contains an <installation> element for each Agent instance. In addition, the <global> element can be used in a homogeneous environment to specify parameters that will be applied to all Agent installations. If a parameter is specified in the <global> element and in an individual <installation> element then the setting for the individual element will overwrite the global setting.

The following configuration steps should be carried out:

Specify the Global global parameters:Specify the path to the YADE settings file (.ini file) in the Batch Installer configuration file with the element <globals><transfer><settings>. the <globals><transfer><settings> element. Specify the <install_path> to point to the location where the Agent should be installed.You could set a different installation path for every installation. In that case, this element should be included for every installation and not globally set. Specify the filename (not the path) for the Agent that has to be installed with the element <installation_file> element. This filename contains the version of the Agent which you are installing and it is helpful for recognising this version of the installed versionsrecognizing the Agent versions that have been installed.
Specify the installation parameters for each Agent installation:Specify the <install_path> to point to a location where the Agent should be installed.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>: SSH the SSH Host <port>: the SSH port Use the <postprocessing> element to specify the post-processing commands that 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

...

Info

title	Post-processing commands

The SSH login user has to be set to become root in order to execute these commands. Therefore the SSH login user should be included to in sudoers.
These two commands will be executed by the PerformInstall job node, which is the last job node in the job chain. If you want to add more commands, please add the call to the job node.
Note that the values for the elements defined in the Batch Installer configuration file can be used for the postprocessing commands, for instance:
- ${install_path}: the value for the element <install_path>
- ${agent_options.scheduler_http_port}: the value for the element <scheduler_http_port>. If not defined, the default value (4445 in this case) is taken, as in the example below.

An example The Batch Installer configuration file for the installation of two Agents is attached on this wiki page (downloadexample can be downloaded here: batch_installer_config_file.xml) and might look like this and is listed in the following code block:

Code Block

language	xml
title	Installer Configuration File
collapse	true

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installations lastRun="2015-11-23 12:11">
    <globals>
        <install_path>/opt</install_path>
        <transfer>
            <settings>C:\Program   <settings>c:\tmp\agent_batchFiles (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer\yade_agent_batch_installer_settings.ini</settings>
        </transfer>
        <ssh>
            <auth_method>password</auth_method>
            <port>22</port>
        </ssh>
		<installation_file><![CDATA[jobschedulerfile>jobscheduler_unix_universal_agent.1.10.2-SNAPSHOT.tar.gz]]><gz</installation_file>
    </globals>
    <installation lastRun="2015-11-23 11:11">
        <agent_options>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>192.11.0.111</host>
        </ssh>
        <postprocessing>
            <command>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}</command>
            <command>echo ${ssh.sudo_password} | sudo -S chkconfigupdadte-rc.d jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    </installation>
    <installation lastRun="2015-11-23 11:11">
        <agent_options>
            <scheduler_http_port>4446</scheduler_http_port>
            <scheduler_user>sos</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>sos</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>192.11.0.111</host>
        </ssh>
        <postprocessing>
            <command>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}</command>
            <command>echo ${ssh.sudo_password} | sudo -S chkconfigupdate-rc.d jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    </installation>
    <installation lastRun="2015-11-23 11:11">
        <agent_options>
            <scheduler_user>sos</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>sos</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>192.11.0.95</host>
        </ssh>
        <postprocessing>
            <command>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}</command>
            <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    </installation>
    <installation lastRun="2015-11-23 11:11">
        <agent_options>
            <scheduler_http_port>4446</scheduler_http_port>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>192.11.0.95</host>
        </ssh>
        <postprocessing>
            <command>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}</command>
            <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    </installation>
</installations>

Info

title

...

Hints

Note that if the port was not specified with the <installations><installation><agent_options><scheduler_http_port> element, this would mean that the global value of 4445 would be applied to all Agent installations. In this example, this element is superfluous for the first and the third installation.
The commands defined under <command> (in the section <installations><installation><postprocessing><command>) are executed for each installation individually. In this example the Agents are installed on different UNIX distributions, the first two Agents would be installed on an Ubuntu distribution (and therefore commands such as update-rc.d are used) and the last two Agents would be installed on a CentOS distribution (and therefore commands such as chkconfig are used).

Excerpt Include

	Batch Installation - Use Cases - Homogeneous environment
	Batch Installation - Use Cases - Homogeneous environment
nopanel	true

Then XML Editor can be used to manage the installation configuration file and the YADE profiles for the transfer of the installation files as well.

Find more details from our XML Editor section.

After download of the XML Editor, extract the zip file, then start "sos.xml.editor.exe"
Open your installer configuration file and assign the XSD schema scheduler_universal_agent_installations.xsd

Please see the following examples (one example for each file):

Image Removed

Space shortcuts

Page tree

Versions Compared

Old Version 16

New Version Current

Key

Introduction

Article Scope

Installation Environment

Installation Procedure

1. Download and Extract the Batch Installer and Agent Files

2. Configure the Transfer of the Universal Agent Installation Files and the Installation of the Agents

2.1 Edit the XML Configuration files

Configuration

XML files

`2.2 Configure the JobScheduler Jobs`

`3 Installation of the Agents`

`Example: Installation of four Agents on two Servers`

Anchor
yade_profile_transfer
yade_profile_transfer
`YADE`

`Configuration File for File Transfer`

Anchor
yade_settings_file
yade_settings_file
`YADE Settings File for File Transfer`

Anchor
installer_config_file
installer_config_file
`Batch Installer Configuration File`

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 16

New Version Current

Key

Introduction

Article Scope

Installation Environment

Installation Procedure

1. Download and Extract the Batch Installer and Agent Files

2. Configure the Transfer of the Universal Agent Installation Files and the Installation of the Agents

2.1 Edit the XML Configuration files

Configuration

XML files

2.2 Configure the JobScheduler Jobs

3 Installation of the Agents

Example: Installation of four Agents on two Servers

Anchoryade_profile_transferyade_profile_transferYADE

Configuration File for File Transfer

Anchoryade_settings_fileyade_settings_fileYADE Settings File for File Transfer

Anchorinstaller_config_fileinstaller_config_fileBatch Installer Configuration File

`2.2 Configure the JobScheduler Jobs`

`3 Installation of the Agents`

`Example: Installation of four Agents on two Servers`

Anchor
yade_profile_transfer
yade_profile_transfer
`YADE`

`Configuration File for File Transfer`

Anchor
yade_settings_file
yade_settings_file
`YADE Settings File for File Transfer`

Anchor
installer_config_file
installer_config_file
`Batch Installer Configuration File`