Table of Contents |
---|
Scenario
Let be the following scenario:
- One JobScheduler Master is running.
- N different servers, where K JobScheduler Universal Agent instances have to be installed on each server.
- The ports where the JobScheduler Universal Agents will be running are the NOT the same ones
- The users, which the JobScheduler Universal Agents is running under are NOT named the same.
- There has been no previous JobScheduler Universal Agents installations on the N servers.
Installation and Configuration Steps
For both scenarios above, the same steps will be carried out:
- Download the JobScheduler Universal Agent Batch Installer zip File
Unzip the JobScheduler Universal Agent Batch Installer zip file.
- Download the JobScheduler Universal Agent installation file.
- Copy the content of the
live
folder to thelive
folder of your JobScheduler Master instance - Copy the content of the folder
batch_install
to any folder (where the JobScheduler has permissions to access) - Copy the JobScheduler Universal Agent installation file to the same folder (mentioned in step 5) and rename the JobScheduler Universal Agent installation file to
jobscheduler_unix_universal_agent.tar.gz
- Create the installer configuration file (see paragraph below Installer Configuration File)
- Job
AgentBatchInstaller:
Adjust the parameter values for the JobAgentBatchInstaller
in your JobScheduler Master - Create the YADE settings file (see section below YADE profiles for the file transfer)
Example: Extra Installation after 2 Agents on 2 Servers
The following example describes how to do the installation of two JobScheduler Universal Agents in two Servers, that is, one JobScheduler Universal Agent installed per Server.
Anchor | ||||
---|---|---|---|---|
|
The installer configuration file contains an <installation>
element for each JobScheduler Universal Agent instance. Set the name for the YADE settings file in the installer configuration file with the element <globals><transfer><settings>.
An example for the installer configuration file can look like this:
Code Block | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
<?xml version="1.0" encoding="utf-8"?> <installations lastRun="2015-11-19 17:11"> <globals> <transfer> <settings><![CDATA[c:\tmp\agent_batch\yade_agent_batch_installer_settings.ini]]></settings> </transfer> </globals> <installation lastRun="2015-11-19 17:11"> <install_path><![CDATA[/opt]]></install_path> <agent_options> <scheduler_http_port>4447</scheduler_http_port> <scheduler_user><![CDATA[test]]></scheduler_user> <scheduler_log_dir><![CDATA[/var/log/sos-berlin.com/jobscheduler/agent]]></scheduler_log_dir> </agent_options> <ssh> <password><![CDATA[test]]></password> <sudo_password><![CDATA[xxxx]]></sudo_password> <auth_method><![CDATA[password]]></auth_method> <host><![CDATA[192.11.0.111]]></host> <port><![CDATA[22]]></port> </ssh> <postprocessing> <command><![CDATA[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><![CDATA[echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}]]></command> </postprocessing> </installation> <installation lastRun=""> <install_path><![CDATA[/opt]]></install_path> <agent_options> <scheduler_http_port>4448</scheduler_http_port> <scheduler_user><![CDATA[test]]></scheduler_user> <scheduler_log_dir><![CDATA[/var/log/sos-berlin.com/jobscheduler/agent]]></scheduler_log_dir> </agent_options> <ssh> <password><![CDATA[test]]></password> <sudo_password><![CDATA[xxxx]]></sudo_password> <auth_method><![CDATA[password]]></auth_method> <host><![CDATA[192.11.0.111]]></host> <port><![CDATA[22]]></port> </ssh> <postprocessing> <command><![CDATA[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><![CDATA[echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}]]></command> </postprocessing> </installation> <installation lastRun="2015-11-19 17:11"> <install_path><![CDATA[/opt/]]></install_path> <agent_options> <scheduler_http_port>4445</scheduler_http_port> <scheduler_user><![CDATA[sos]]></scheduler_user> <scheduler_log_dir><![CDATA[/var/log/sos-berlin.com/jobscheduler/agent]]></scheduler_log_dir> </agent_options> <ssh> <user><![CDATA[sos]]></user> <password><![CDATA[xxxx]]></password> <sudo_password><![CDATA[xxxx]]></sudo_password> <auth_method><![CDATA[password]]></auth_method> <host><![CDATA[192.11.0.95]]></host> <port><![CDATA[22]]></port> </ssh> <postprocessing> <command><![CDATA[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><![CDATA[echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}]]></command> </postprocessing> </installation> </installations> |
Anchor | ||||
---|---|---|---|---|
|
Each installation makes use of a profile in the YADE settings file. The default profile name is <host>:<port>
where
...
- Note that this is a XML file and YADE will expect an INI file to do the transfer, as we indicated in the installer configuration file (in the section
<globals><install_path><transfer><settings>
).- It is recommended to use the XML Editor for converting from XML to INI format (see below paragraph Using the XML Editor)
- Here is an example of an INI file, converted from the XML file attached above:
Code Block title INI file collapse true [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.95:4445] protocol = sftp host = 192.11.0.95 user = sos 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.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/
Anchor | ||||
---|---|---|---|---|
|
Then XML Editor can be used to manage the installation configuration file and the YADE profiles for the transfer of the installation files as well.
...