Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The following steps have to be carried out. Files All the files mentioned in this section can be downloaded from downloadedfrom http://www.sos-berlin.com/jobscheduler-downloads

...

  1. 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>.
  2. 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>.
  3. 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 to this page (downloadexample can be downloaded hereyade_agent_batch_installer_settings.xml) and is shown in the following code block:

...

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 and assigned the scheduler_universal_agent_installations.xsd XSD schema. The XML file contains a basic example with recommended values for an Agent installation.

...

Info
titlePost-processing commands
  • The SSH login user has to be set to root in order to execute these commands. Therefore the SSH login user should be included 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 to this page (downloadexample can be downloaded herebatch_installer_config_file.xml) and is shown listed in the following code block:

...