Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Alan Amos

Saved on

compared with

New Version 3

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor corrections to text

...

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.

  • 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> element

    • ${agent_options.scheduler_http_port}: the value for the element <scheduler_http_port> element. If this element is not defined, the default value (4445 in this case) is will be taken, as in the example full XML code listing below.

A complete typical installation configuration for a single Agent would be (shown from the root installations element):

  • installations lastRun="2018-01-02 13:01"
    • globals
      • install_path /opt/sos-berlin.com/jobscheduler
      • transfer
        • settings C:\ProgramData\sos-berlin.com\jobscheduler\jobscheduler_1.12\config\batch_install\yade_agent_batch_installer_settings.xml
      • ssh
        • auth_method password
        • port 22
      • installation_file jobscheduler_unix_universal_agent.1.12.0.tar.gz
    • installation lastRun="2018-01-02 13:01"
      • agent_options
      • ssh
        • user sos
        • password sos
        • sudo_password sos
        • host 192.11.0.202
      • 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 echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler_agent_${agent_options.scheduler_http_port} defaults

Note that in the above example two of the SSH elements (<auth_method> and <port>) are configured globally and three four (<user>, <password>, <sudo_password> and <host>) are configured individually for each Agent.

...

The following code block shows Batch Installer configuration file for installing two agents. This file has therefore two installation elements and fewer elements defined in the <globals> section than the typical installation configuration for a single Agent shown above.

...