Page History

...

The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads Status

1. Unix
   • Download the "JobScheduler Universal Agent" tarball for Unix.
   • Download the "JobScheduler Universal Agent Batch Installer" for Unix. The archive contains the following: 
     • a config/live/batch_installer_agent folder, with the jobs and job chainsextract . Extract these files to the live folder of the JobScheduler Master: SCHEDULER_DATA/config/live.
     • a config/batch_installer folder containing configuration files for the Batch Installer. These Extract these files should be extracted to the config directory of the JobScheduler Master: SCHEDULER_DATA/config.
     • Copy the JobScheduler Universal Agent installation file to the SCHEDULER_DATA/config/batch_installer folder.
       
2. Windows
   • Download the "JobScheduler Universal Agent" for Windows.
   • Download the "JobScheduler Universal Agent Batch Installer" for Windows. The archive contains the following:
     • the config/live/batch_installer_agent folder with jobs and job chains that should be extracted . Extract these files to the live folder of the JobScheduler Master SCHEDULER_DATA/config/live.
     • the config/batch_installer folder with configuration files for the Batch Installer that should be extracted . Extract these files to the JobScheduler configuration directory SCHEDULER_DATA/config.
     • Copy the JobScheduler Universal Agent installation file to the folder SCHEDULER_DATA/config/batch_installer.

...

Configuring XML files with a text editor is error-prone . Therefore and we recommend that you download the XML Editor that can be used to manage the configuration files required for the Batch Installer and . The XML Editor automatically validates files and thereby reduces the possibility of configuration errors. For details about the XML Editor see the Using the XML Editor chapter below.

...

• <host> will be substituted with the value from the <installation><agent_option><scheduler_ip_address> element and
• <port> will be substituted with the value from the <installation><agent_option><scheduler_http_port> element.

Please take Now carry out the following steps:

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.

...

The Batch Installer configuration file contains an <installation> element for each Agent instance. In addition, the <global> element can be used in a homogeneous environment to specify parameters that will be applied to all Agent installations. If a parameter is specified in both the <global> element and in an individual <installation> element then the setting for the individual element will overwrite the global setting.

...

1. Specify the Global parameters:
   • Specify the <install_path> to point to a location where the Agent should be installed.

   • Specify the path to the YADE settings file (.ini file) in the Batch Installer configuration file with the element <globals><transfer><settings>. 

   • Specify the credentials for the SSH connection:

     • <user>: SSH login user 
     • <password>: Password for the login user
     • <sudo_password>: Password for sudo actions
     • <auth_method>: SSH authentication method
     • <port>: SSH port 

   • Specify the filename (not the path) for the Agent that has to be installed with the element  <installation_file> element. This filename contains the version of the Agent which you are installing and it is helpful for recognising this recognizing the version of the Agents that are installed versions.

   • 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
2. Specify the installation parameters for each Agent installation:
   • Agent options:
     • <scheduler_user>: the Agent user
     • <scheduler_log_dir>: the Logs folder for the Agent
   • <host>: SSH Host 
     
     

An example Batch Installer configuration file for the installation of two Agents is attached on this wiki page (download: batch_installer_config_file.xml) and might look like thisis shown in the following code block:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<installations lastRun="2015-11-20 14:11">
    <globals>
        <install_path>/opt</install_path>
        <transfer>
            <settings>C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer\yade_agent_batch_installer_settings.ini</settings>
        </transfer>
        <ssh>
			<user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <auth_method>password</auth_method>
            <port>22</port>
        </ssh>
  	    <installation_file><![CDATA[jobscheduler_unix_universal_agent.1.10.2-SNAPSHOT.tar.gz]]></installation_file>
        <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 update-rc.d jobscheduler_agent_${agent_options.scheduler_http_port} defaults</command>
        </postprocessing>
    </globals>
    <installation lastRun="2015-11-20 14:11">
        <agent_options>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <host>xxxx</host>
        </ssh>
    </installation>
    <installation lastRun="2015-11-20 14:11">
        <agent_options>
            <scheduler_user>test</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <host>xxxx</host>
        </ssh>
    </installation>
</installations>

...

...