You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Scenarios

An ...

Scenario 1: Fresh Agent installation where same conditions in each Agent server

Let be the following scenario:

  • One JobScheduler Master is running.
  • N different servers, where ONE JobScheduler Universal Agent instance has to be installed (Agent server). 
  • The ports where the JobScheduler Universal Agents will be running are the same ones.
  • The users, which the JobScheduler Universal Agents is running under, are named the same.
  • There has been no previous JobScheduler Universal Agents installations on these N servers.

Scenario 2: Agent Update where same conditions in each Agent server

Let be the following scenario:

  • One JobScheduler Master is running.
  • N different servers, where ONE JobScheduler Universal Agent instance has to be installed. 
  • The ports where the JobScheduler Universal Agents will be running are the same ones 
  • The users, which the JobScheduler Universal Agents is running under are named the same.
  • It is NOT a fresh installation, instead it is an update of the JobScheduler Universal Agents that have been already installed on the servers

Installation and Configuration Steps

Unzip the JobScheduler Universal Agent Batch Installer zip file.

  1. Download the JobScheduler Universal Agent Batch Installer zip File
    1. http://download.sos-berlin.com/JobSchedulerAgent/jobscheduler_universal_agent_batch_install.zip
  2. Download the JobScheduler Universal Agent installation file.
    1. https://www.sos-berlin.com/jobscheduler-downloads 
  3. Copy the content of the live folder to the live folder of a JobScheduler instance
  4. Copy the content of the folder batch_install to any folder
  5. Copy the JobScheduler Universal Agent installation file to the same folder
  6. Rename the JobScheduler Universal Agent installation file to jobscheduler_unix_universal_agent.tar.gz
  7. Create the installer configuration file
  8. Adjust the parameter values for the job AgentBatchInstaller
  9. Set the name for the YADE settings file in the installer configuration file with the element <globals><transfer><settings>
  10. Create the YADE settings file 
    1. Add a <ProtocolFragments> element and nodes for each host that you want to install the JobScheduler Universal Agent for.
    2. Add a <Profile> element and nodes for each host that you want to install the JobScheduler Universal Agent for.

Installer Configuration File

The installer configuration file contains an <installation> element for each JobScheduler Universal Agent instance.

A minimal example for the installer configuration file can look like this:

<?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:\tmp\agent_batch\yade_agent_batch_installer_settings.ini</settings>
        </transfer>
        <ssh>
            <auth_method>password</auth_method>
            <port>22</port>
        </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>
    </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>
            <user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>xxxx</host>
        </ssh>
    </installation>
    <installation lastRun="2015-11-20 14:11">
        <agent_options>
            <scheduler_user>sos</scheduler_user>
            <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir>
        </agent_options>
        <ssh>
            <user>sos</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <host>xxxx</host>
        </ssh>
    </installation>
</installations>

YADE profiles for the file transfer

Each installation makes use of a profile in the YADE settings file. The default profile name is <host>:<port> where

  • <host> will be substituted with the value from the element <installation><agent_option><scheduler_ip_address>
  • <port> will be substituted with the value from the element <installation><agent_option><scheduler_http_port>
  1. Specify the name of the YADE settings file with the <globals><settings> element.
  2. Open the YADE settings file or create a new one.
  3. Assign the XSD Schema http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd
  4. Add a <ProtocolFragments> element and nodes for each host that you want to install the JobScheduler Universal Agent for.
  5. Add a <Profile> element and nodes for each host you want install the JobScheduler Universal Agent for.
  6. The default profile_id is <host>:<port>. If you do not use the default then you have to specify the profile name in the installer configuration file.
  • No labels