Page History

...

The Batch Installer configuration file contains an <installation> element for each Agent instance. Since it is a homogeneous environment, lots of parameters can be set in the <global> section and they are valid for all Agent installations. If a parameter set in global and 

Please configure as follows:

1.  Set the name for the YADE settings file in the Batch Installer configuration file with the element <globals><transfer><settings>.
2. Set install_path, where the Agent is going to be installed.
3. 


•  For any further information about the parameters have a look at (Tabelle mit Parametern machen!)

...

<?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>
			<user>test</user>
            <password>xxxx</password>
            <sudo_password>xxxx</sudo_password>
            <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>
            <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>

HintHints:

•  Note that no port is indicated here, that is, the parameter <scheduler_http_port> is not indicated here (in the section <installations><installation><agent_options>) . That is a very useful configuration in case the ports selected for the different JobScheduler Universal Agent would be all 4445, which is the default value. So for that example, all JobScheduler Universal Agents will be running on the port 4445 (in their Agent server respectively).
• Since it is a homogeneous environment, lots of parameters can be set in the <global> section and they are valid for all Agent installations.

Anchor
yade_
Anchor
yade_profile_transfer yade_profile_transfer

YADE Configuration File for File Transfer

=> Wo liegt die Beispiel-Datei?

As mentioned above in the chapter Configuration, you should have opened your Batch Installer configuration file batch_installer_config_file.xml and assigned it the XSD schema scheduler_universal_agent_installations.xsd. The XML file contains a basic example with the recommended values for an Agent installation (of only one Agent).

The Batch Installer configuration file contains an <installation> element for each Agent instance. Set the name for the YADE settings file in the Batch Installer configuration file with the element <globals><transfer><settings>.

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

...