...
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>.
- Specify the
<install_path>
to point to a 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>
. This filename contains the version of the Agent which you are installing and it is helpful for recognising this version of the installed versions.
- Specify the installation parameters for each Agent installation:
- Specify the
- Agent options:
<scheduler_user>
: Agent user<scheduler_log_dir>
: Logs folder for the Agent
Specify the credentials for the SSH connection:
<user>
: SSH login user<password>
: Password for the login user<sudo_password>
: Password forsudo
actions- <
auth_method>
: SSH authentication method - <
host
>: SSH Host <port>
: 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
<install_path>
to point to a location where the Agent should be installed. - Agent options:
...
Info | ||
---|---|---|
| ||
|
Anchor | ||||
---|---|---|---|---|
|
Then The XML Editor can be used to manage the installation Batch Installer 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):
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:
Anchor | ||||
---|---|---|---|---|
|
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.