...
| Code Block | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
<?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:\tmp\agent_batch\yade_agent_batch_installer_settings.ini</settings>
</transfer>
<ssh>
<auth_method>password</auth_method>
<port>22</port>
</ssh>
</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 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>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 chkconfig 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>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="">
<agent_options>
<scheduler_http_port>4448</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.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 chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
</postprocessing>
</installation>
</installations> |
...
The XML Editor can be used to manage the Batch Installer configuration file and the YADE configuration file.
XML Editor for Batch Installer configuration file
An example Batch Installer configuration file for the installation of a single Agent is shown in the following screenshot:
XML Editor for YADE configuration file
An example YADE configuration file for the installation of a single Agent is shown in the next screenshot:
...
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
The "YADE Xml2Ini Converter" function in the XML Editor is available for converting YADE files from XML to the .ini format required by versions of YADE before 1.11. Clicking on the button of the same name will open the following form:
Note that it is not necessary to create a Profile for the Batch Installer, as conversion will take place automatically once the "Autotransform" option has been chosen. Every time a change in the XML file is saved the XML file will be automatically converted and saved in .ini format.
A pop-up window will show every time a change is saved if the option "Show notification on autotransform" is chosen.