Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 19

changes.mady.by.user Victor Garcia-Beltran

Saved on

compared with

New Version 20

changes.mady.by.user Victor Garcia-Beltran

Saved on

Key

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

...

  1. Open a JobScheduler Operating Center (JOC) browser window for the JobScheduler master.
  2. Go on the "Jobs" Window and open the "batch_installer_universal_agent" folder.
  3. Right click on the job to open the context menu.
  4. Select the Start task immediately operation.
  5. This job will create the appropriate JobScheduler orders as explained in the chapter Batch Installer Application.

Example: Installation of one extra JobScheduler Universal Agent

...

 

 

...



Code Block
titleINI file
collapsetrue
[protocol_fragment_sftp@SFTP_192.11.0.111:4445]
protocol                            = sftp
host                                = 192.11.0.111
user                                = test
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.111:4446]
protocol                            = sftp
host                                = 192.11.0.111
user                                = sos
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.95:4445]
protocol                            = sftp
host                                = 192.11.0.95
user                                = sos
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.95:4446]
protocol                            = sftp
host                                = 192.11.0.95
user                                = sos
ssh_auth_method                     = password
password                            = xxxx
[protocol_fragment_sftp@SFTP_192.11.0.111:4448]
protocol                            = sftp
host                                = 192.11.0.111
user                                = test
ssh_auth_method                     = password
password                            = xxxx
[192.11.0.111:4445]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.111:4445
target_dir                          = /home/test/tmp/
[192.11.0.111:4446]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.111:4446
target_dir                          = /home/sos/tmp/
[192.11.0.95:4445]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.95:4445
target_dir                          = /home/sos/tmp/
[192.11.0.95:4446]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.95:4446
target_dir                          = /home/test/tmp/
[192.11.0.111:4448]
operation                           = copy
source_protocol                     = local
file_spec                           = .*\.(sh|gz)$
source_dir                          = C:\tmp\agent_batch
target_include                      = protocol_fragment_sftp@SFTP_192.11.0.111:4448
target_dir                          = /home/test/tmp/

...

  1. Leave the global parameters as they were set for your previous Use Case.
  2. Specify the installation parameters for the extra Agent installation:
    • Set lastRun element to an empty value (with the element <installations><installation>). This is the value that will make the Batch Installer just carry out this one extra installation and skip the rest.
    • Agent options:
      • <scheduler_user>: the Agent user
      • <scheduler_log_dir>: the Logs folder for the Agent

    • Specify the credentials for the SSH connection:

      • <user>: the SSH login user 
      • <password>: the Password for the login user
      • <sudo_password>: the Password for sudo actions
      • <auth_method>: the SSH authentication method
      • <host>: the SSH Host
      • <port>: the SSH port 
    • Use the <postprocessing> element to specify the post-processing commands 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
language
Code Block
Info
xmltitleInstaller Configuration File
linenumberstrue
collapsetrue
Post-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 Batch Installer configuration file for the installation of two Agents is attached to this page (download: batch_installer_config_file.xml) and is shown in the following code block:

Code Block
languagexml
titleInstaller Configuration File
linenumberstrue
collapsetrue
<?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<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installations lastRun="2015-11-23 1211:11">
    <globals>
     <agent_options>
   <install_path>/opt</install_path>
         <transfer><scheduler_user>test</scheduler_user>
            <settings>c:\tmp\agent_batch\yade_agent_batch_installer_settings.ini</settings><scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </transfer>agent_options>
        <ssh>
            <auth_method>password</auth_method><user>test</user>
            <port>22<<password>xxxx</port>password>
            </ssh>
<sudo_password>xxxx</sudo_password>
     </globals>
     <installation lastRun="2015-11-23 11:11"> <host>192.11.0.111</host>
        <agent_options></ssh>
        <postprocessing>
      <scheduler_user>test</scheduler_user>
      <command>echo ${ssh.sudo_password} | sudo -S cp <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>${install_path}/jobscheduler_agent/bin/jobscheduler_agent_${agent_options.scheduler_http_port}.sh /etc/init.d/jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        <ssh>
    <command>echo ${ssh.sudo_password} | sudo -S    <user>test</user>chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    <password>xxxx<</password>installation>
    <installation        <sudo_password>xxxx</sudo_password>lastRun="2015-11-23 11:11">
        <agent_options>
    <host>192.11.0.111</host>
        </ssh><scheduler_http_port>4446</scheduler_http_port>
        <postprocessing>
     <scheduler_user>sos</scheduler_user>
       <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> <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
      <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command> <user>sos</user>
        </postprocessing>
    <<password>xxxx</installation>password>
    <installation lastRun="2015-11-23 11:11">
        <agent_options><sudo_password>xxxx</sudo_password>
            <scheduler_http_port>4446</scheduler_http_port><host>192.11.0.111</host>
        </ssh>
    <scheduler_user>sos</scheduler_user>
    <postprocessing>
            <command>echo <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>${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>
        <ssh>
    <command>echo ${ssh.sudo_password} | sudo -S    <user>sos</user>chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
            <password>xxxx</password></postprocessing>
            <sudo_password>xxxx</sudo_password></installation>
    <installation        <host>192.11.0.111</host>lastRun="2015-11-23 11:11">
        </ssh><agent_options>
        <postprocessing>
     <scheduler_user>sos</scheduler_user>
       <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> <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
    <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        <user>sos</user>
           < <password>xxxx</postprocessing>password>
    </installation>
        <sudo_password>xxxx</sudo_password>
          <installation lastRun="2015-11-23 11:11">
 <host>192.11.0.95</host>
        </ssh>
   <agent_options>
     <postprocessing>
       <scheduler_user>sos</scheduler_user>
     <command>echo ${ssh.sudo_password} | sudo -S cp  <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>${install_path}/jobscheduler_agent/bin/jobscheduler_agent_${agent_options.scheduler_http_port}.sh /etc/init.d/jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        <ssh>
    <command>echo ${ssh.sudo_password} | sudo -S    <user>sos</user>chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </postprocessing>
    <password>xxxx<</password>installation>
    <installation        <sudo_password>xxxx</sudo_password>lastRun="2015-11-23 11:11">
        <agent_options>
    <host>192.11.0.95</host>
        </ssh><scheduler_http_port>4446</scheduler_http_port>
        <postprocessing>
    <scheduler_user>test</scheduler_user>
        <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>
 <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
      <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command> <user>sos</user>
        </postprocessing>
    <password>xxxx</password>
      </installation>
    <installation lastRun="2015-11-23 11:11"> <sudo_password>xxxx</sudo_password>
        <agent_options>
    <host>192.11.0.95</host>
        <scheduler_http_port>4446</scheduler_http_port></ssh>
        <postprocessing>
    <scheduler_user>test</scheduler_user>
        <command>echo ${ssh.sudo_password} | sudo -S cp <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>sos</user>${install_path}/jobscheduler_agent/bin/jobscheduler_agent_${agent_options.scheduler_http_port}.sh /etc/init.d/jobscheduler_agent_${agent_options.scheduler_http_port}</command>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password><command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
            <host>192.11.0.95</host>
    </postprocessing>
    </ssh>installation>
	<installation lastRun="">
        <postprocessing><agent_options>
            <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>4448</scheduler_http_port}</command>
port>
            <scheduler_user>test</scheduler_user>
      <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler<scheduler_agent_${agent_options.scheduler_http_port}</command>log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </postprocessing>
agent_options>
       </installation>
	<installation lastRun="">
 <ssh>
            <agent_options><user>test</user>
            <scheduler_http_port>4448</scheduler_http_port><password>xxxx</password>
            <scheduler<sudo_user>test<password>xxxx</schedulersudo_user>password>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir><host>192.11.0.111</host>
        </agent_options>ssh>
        <ssh><postprocessing>
                <user>test</user><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>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>192.11.0.111</host><command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command>
        </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>postprocessing>
    </installation>
</installations>

Anchor
xml_editor
xml_editor
Using the XML Editor

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:

Image Added

XML Editor for YADE configuration file

An example YADE configuration file for the installation of a single Agent is shown in the next screenshot:

Image Added

Anchor
yadexml2ini_converter
yadexml2ini_converter
XML Editor for converting YADE configuration files (XML) into YADE setting files (.ini)

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:

Image Added

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.