| Table of Contents |
|---|
Environment
...
We define an homogeneous environment as an environment where the JobScheduler Universal Agents will be installed under the same conditions:
...
| Anchor | ||||
|---|---|---|---|---|
|
Wo finde ich eine Beispiel-Datei?As mentioned above in the chapter Configuration, you should have opened your Batch Installer configuration file batch_installer_config_file.xml and assigned it the XSD schema scheduler_universal_agent_installations.xsd. The XML file contains a basic example with the recommended values for an Agent installation (of only one Agent).
The Batch Installer configuration file contains an <installation> element for each Agent instance. Set the name for the YADE settings file in the Batch Installer configuration file with the element <globals><transfer><settings>.
- For any further information about the parameters have a look at (Tabelle mit Parametern machen!)
...
An example for the Batch Installer configuration file in case two agents want to be installed looks An example for the installer configuration file can look like this:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installations lastRun="2015-11-20 14:11">
<globals>
<install_path>/opt</install_path>
<transfer>
<settings>c:\tmp\agent_batch\yade_agent_batch_installer_settings.ini</settings>
</transfer>
<ssh>
<user>test</user>
<password>xxxx</password>
<sudo_password>xxxx</sudo_password>
<auth_method>password</auth_method>
<port>22</port>
</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>
</globals>
<installation lastRun="2015-11-20 14:11">
<agent_options>
<scheduler_user>test</scheduler_user>
<scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
</agent_options>
<ssh>
<host>xxxx</host>
</ssh>
</installation>
<installation lastRun="2015-11-20 14:11">
<agent_options>
<scheduler_user>test</scheduler_user>
<scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
</agent_options>
<ssh>
<host>xxxx</host>
</ssh>
</installation>
</installations> |
HintsHint: Note that no port is indicated here, that is, the parameter <scheduler_http_port> is not indicated here (in the section <installations><installation><agent_options>) . That is a very useful configuration in case the ports selected for the different JobScheduler Universal Agent would be all 4445, which is the default value. So for that example, all JobScheduler Universal Agents will be running on the port 4445 (in their Agent server respectively).
...
| Anchor | ||||
|---|---|---|---|---|
|
...