Table of Contents |
---|
Environment
We consider a homogeneous environment a scenario in which a number of JobScheduler Agents will be installed based on the same prerequisites:
- A JobScheduler Master is up and running.
- Agent installations are performed for an arbitrary number of servers with the same operating system. One Agent is installed per server.
- Agents are operated with the same user, listening port and installation path.
The Batch Installer supports
- First Installation: no Agent is installed and running on the server.
- Update Installation: an Agent is installed and optionally up and running.
Structure
The JobScheduler Agents will be installed from a JobScheduler Master that connects to the Agent Servers to execute the corresponding Agent installations. The structure is formed by a JobScheduler job AgentBatchInstaller
and a JobScheduler job chain universal_agent_installer
. The job AgentBatchInstaller
is responsible for creating the JobScheduler orders for the job chain. These orders are named <host>:<port>
meaning the port and the host where an Agent will be installed. The job chain have four nodes and the sequence look like this:
...
The job chain for update/installation of an Agent uses the nodes:
CheckPreRequisite
Sync:
To wait until all prerequisites are checked and all instances have been shut down.- Checking for the correct Java version
- Checking whether JobScheduler Universal Agent already has been installed.
- If so
- shutting down a possibly running instance
- remove the installation
- If so
TransferInstallationSetup
: To transfer the installer files to the host- Before the transfer starts, the preprocessor will create the start script for the Agent instance from the template
jobscheduler_agent_instance_script.txt
The files that will be transfered are specified with the configuration element
<globals><transfer><file_spec=".*\.(sh|gz)$">
- With this regular expression, the following files will be transfered:
- the JobScheduler Universal Agent installer files:
jobscheduler_unix_universal_agent.tar.gz
- the instance start script:
jobscheduler_agent_<port>.sh
- the installation script:
jobscheduler_universal_agent_install.sh
- the JobScheduler Universal Agent installer files:
- Before the transfer starts, the preprocessor will create the start script for the Agent instance from the template
PerformInstall
: To start the installation using SSH.- The step before transfered installation script will be executed
- The installation script will install and start the JobScheduler Universal Agent
- Finally the post-processing commands will be executed
- The post-processing commands are stored with the element
<installation><postprocessing><command>
- Three commands will be executed
- if you have more than three commands, please add the call in the job
PerformInstall
- if you have more than three commands, please add the call in the job
- The default commands will place the Agent start script under
/etc/init.d
and will setup the autostart for JobScheduler Universal Agent on a Linux server (example for an Ubuntu distribution):echo ${ssh.sudo_password} | sudo -S cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler
echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defaults
- The post-processing commands are stored with the element
Download
The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads
- Unix
- Download the "JobScheduler Universal Agent" tarball for Unix.
- Download the "JobScheduler Universal Agent Batch Installer" for Unix. The archive provides the following content:
- the
config/live/batch_installer_agent
folder contains jobs and job chains that should be extracted to thelive
folder of the JobScheduler Master${SCHEDULER_DATA}/config/live
. - the
config/batch_installer
folder contains configuration files for the Batch Installer that should be extracted to theconfig
directory of the JobScheduler Master$
{SCHEDULER_DATA}/config
. - Copy the JobScheduler Universal Agent installation file to the folder
$
{SCHEDULER_DATA}/config/
batch_installer.
- the
- Windows
- Download the "JobScheduler Universal Agent" for Windows.
- Download the "JobScheduler Universal Agent Batch Installer" for Windows. The archive provides the following content:
- the
config/live/batch_installer_agent
folder contains jobs and job chains that should be extracted to thelive
folder of the JobScheduler Master${SCHEDULER_DATA}/config/live
. - the
config/batch_installer
folder contains configuration files for the Batch Installer that should be extracted to the JobScheduler configuration directory$
{SCHEDULER_DATA}/config
. - Copy the JobScheduler Universal Agent installation file to the folder
$
{SCHEDULER_DATA}/config/
batch_installer
.
- the
Configuration
XML files
...
Introduction
The JobScheduler Universal Agent Batch Installer is a set of files used together by a JobScheduler Master to install the Universal Agent on local and remote servers.
This article is one of a series describing how to configure the JobScheduler Universal Agent Batch Installer so that a number of Universal Agents can be readily installed on a number of servers.
Article Scope
This article describes how to use the Universal Agent Batch Installer to install Agents in a homogeneous environment. Other use cases in this series of articles are listed in the introductory JobScheduler Universal Agent - Batch Installation and Update of Agents article.
A general introduction to installation of the JobScheduler Universal Agent can be found in the JobScheduler Universal Agent - Installation & Operation article.
The JobScheduler Universal Agent - Batch Installation and Update of Agents article provides an overview of how the Batch Installer works. New users are strongly recommended to read this article before proceeding with the instructions presented here.
The Batch Installation - Reference Documentation article provides a detailed guide to configuration of the batch installer with, for example, full lists of parameters.
Installation Environment
This article describes the use of the JobScheduler Universal Agent Batch Installer in a homogeneous environment - that is an environment in which a number of JobScheduler Agents will be installed according to the same prerequisites:
- Requirements for this use case:
- The Agent installations are to be performed on any number of servers that have the same operating system. One Agent is to be installed per server.
- The Agents will be operated with the same user, listening port and installation path.
Installation Procedure
General requirements:
- A JobScheduler Master is up and running.
- A Java Run-time Environment in version 1.8 or newer is installed on the system(s) the Agent is to be installed on.
- We recommend that you use the SOS XML Editor to manage the configuration files required for the Batch Installer. More information about the installation and use of the XML editor will be provided later in this article.
1. Download and Extract the Batch Installer and Agent Files
The following steps have to be carried out. Files can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads
- 1.1 Unix
- Download the "JobScheduler Universal Agent" tarball for Unix.
- Download the "Universal Agent Batch Installer". The archive contains the following folders and sub-folders:
live/batch_install_universal_agent
- This folder contains the Jobs and Job Chain used to carry out the installation.
- Extract these files to the the
live
folder of the JobScheduler Master:SCHEDULER_DATA/config/live
.
batch_install
- This folder contains the configuration files for the Batch Installer.
- Extract these files to the
config
directory of the JobScheduler Master:SCHEDULER_DATA
/config
.
- Copy the JobScheduler Universal Agent installation file to the
SCHEDULER_DATA/config/
batch_install
folder.
- 1.2 Windows
- Download the "JobScheduler Universal Agent" for Windows.
- Download the "Universal Agent Batch Installer". The archive contains the following folders and sub-folders
- the
live/batch_install_universal_agent
folder- This folder contains the Jobs and Job Chain used to carry out the installation.
- Extract these files to the
live
folder of the JobScheduler MasterSCHEDULER_DATA/config/live
.
- the
batch_install
folder- This folder contains the configuration files for the Batch Installer.
- Extract these files to the JobScheduler configuration directory
SCHEDULER_DATA/config
.
- the
- Copy the JobScheduler Universal Agent installation file to the folder
SCHEDULER_DATA/config/
batch_instal
folderl
.
2. Configure the Transfer of the Universal Agent Installation Files and the Installation of the Agents
2.1 Edit the XML Configuration files
Configuring complex XML files with a text editor is often a tedious and error-prone procedure. To get around this, we recommend that you use our XML Editor to manage the configuration files required for the Batch Installer. The XML Editor automatically validates configuration files and therefore reduces the possibility of configuration errors. See the Using the XML Editor chapter below for more detailed information about using the XML Editor.
...
- After downloading the XML Editor, extract the contents of the zip file to a convenient folder (an installation routine is not required) and start the
sos.xml.editor.exe
program. - Use the XML Editor to configure transfer of the Universal Agent installation files:
- Open your
yade_agent_batch_installer_settings.xml
YADE configurationfile, which is located in the
config/batch_installer
folder and assign the following schema in the XML Editor:- http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd.
- See the YADE profiles for the file transfer chapter below for instructions on how to configure the YADE configuration file.
- Open your
- Use the XML Editor to configure the installation of the Universal Agents:
- Open your
batch_installer_config_file.xml
configuration file in the XML Editor and assign the
- Open your
scheduler_universal_agent_installations.xsd
...
- schema: both files are located in
...
- the
config/batch_installer
- the
...
- folder.
- See the Batch Installer Configuration File chapter below for instructions on
- folder.
...
- how to configure the Batch Installer configuration file
...
- .
Info | ||
---|---|---|
|
...
Info | ||
---|---|---|
| ||
|
2.2 Configure the JobScheduler Jobs
...
Once the Job and Job Chain have been extracted to the live
folder of your JobScheduler Master carry out the following:
AgentBatchInstaller
J
ob:- Set
AgentBatchInstaller:
Adjust- the parameter values for the
AgentBatchInstaller
job in your JobScheduler Master. Adjust Set the
installation_definition_file
job parameter with to the path that points to the Batch Installer configuration file.
3 Installation
...
of the Agents
The Agents can be installed after Having configured the XML configuration files and the JobScheduler jobs, the Agents can be installedJobScheduler Jobs have been configured. Start a task for the AgentBatchInstaller
job as follows:
- Open a JobScheduler Operating Center (JOC) browser window for the JobScheduler master.
- Go on the "Jobs" Window and open the "batch_installer_universal_agent" folder.
- Right click on the JobScheduler job From to open the context menu.
- Select the use the operation:
Start task immediately
operation. - This job will create different
- the appropriate Orders for the JobScheduler orders
- as explained in the chapter and the Agent installation
- description of the Batch Installer Application.
Example Use Case: Installation of two Agents
The following example explains describes the installation of two Agents for two servers, i.e. one Agent will be installed per server.
...
on separate servers. First of all, the YADE configuration file for the file transfer will be configured (in XML format), it will then be converted to the YADE settings file format (.ini) and finally the Batch Installer configuration file will be specified.
Anchor | ||||
---|---|---|---|---|
|
We assume that you have opened the yade_agent_batch_installer_settings.xml
YADE configuration file in the XML Editor and assigned the http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd
XSD schema.
A separate profile in the YADE configuration file is required for each Agent installation. The default profile name is <host>:<port>
where:
<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.
Now carry out the following steps:
- 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>
. - 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>
. - 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 contents of the YADE configuration file for the example is listed in the following code block:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="utf-8"?>
<Configurations xsi:noNamespaceSchemaLocation="http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Fragments>
<ProtocolFragments>
<SFTPFragment name="SFTP_192.11.0.111:4445"> |
You should have opened the Batch Installer configuration file batch_installer_config_file.xml
and have assigned the XSD schema scheduler_universal_agent_installations.xsd.
The XML file contains a basic example with the recommended values for an Agent installation.
The Batch Installer configuration file contains an <installation>
element for each Agent instance. For a homogeneous environment parameters can be specified with the <global>
element and will be applied to all Agent installations. If a parameter is available in the <global>
element and in an individual <installation>
element then the setting for the specific installation will overwrite the global setting.
Please, perform the following configuration steps:
- 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 forsudo
actions- <
auth_method>
: SSH authentication method <port>
: SSH port
- Specify the post-processing commands that fit your operating system on the Agent server with the
<postprocessing>
element. The default commands will place the Agent start script under/etc/init.d
and will setup the autostart for JobScheduler Universal Agent on a Linux server (example for an Ubuntu distribution):echo ${ssh.sudo_password} | sudo -S cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler
echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defaults
Info title Post-processing commands The SSH login user has to become root in order to execute these commandos. Therefore the SSH login user should be included to sudoers. - Specify the
- Installation parameters (specified for each Agent installation):
- Agent options:
<scheduler_user>
: Agent user<scheduler_log_dir>
: Logs folder for the Agent
- SSH Host
- Agent options:
An example for the Batch Installer configuration file for the installation of two Agents might look like this:
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><BasicConnection> <settings>C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer\yade_agent_batch_installer_settings.ini</settings><Hostname><![CDATA[192.11.0.111]]></Hostname> </transfer>BasicConnection> <ssh> <user>test</user><SSHAuthentication> <password>xxxx</password><Account><![CDATA[test]]></Account> <sudo_password>xxxx</sudo_password><AuthenticationMethodPassword> <auth_method>password</auth_method><Password><![CDATA[xxxx]]></Password> <port>22<</port>AuthenticationMethodPassword> </ssh>SSHAuthentication> </SFTPFragment> <postprocessing><SFTPFragment name="SFTP_192.11.0.95:4445"> <BasicConnection> <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> <Hostname><![CDATA[192.11.0.95]]></Hostname> </BasicConnection> <command>echo ${ssh.sudo_password} | sudo -S chkconfig jobscheduler_agent_${agent_options.scheduler_http_port}</command> <SSHAuthentication> </postprocessing> </globals> <installation lastRun="2015-11-20 14:11"> <Account><![CDATA[test]]></Account> <agent_options><AuthenticationMethodPassword> <scheduler_user>test</scheduler_user><Password><![CDATA[xxxx]]></Password> <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir></AuthenticationMethodPassword> </agent_options>SSHAuthentication> <ssh></SFTPFragment> </ProtocolFragments> <host>xxxx</host></Fragments> <Profiles> </ssh> <Profile profile_id="192.11.0.111:4445"> <Operation> </installation> <Copy> <installation lastRun="2015-11-20 14:11"> <CopySource> <agent_options> <CopySourceFragmentRef> <scheduler_user>test</scheduler_user> <LocalSource /> <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir> </CopySourceFragmentRef> </agent_options> <SourceFileOptions> <ssh> <Selection> <host>xxxx</host> <FileSpecSelection> </ssh> <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec> </installation> </installations> |
Info | ||
---|---|---|
| ||
|
...
You should have opened your YADE settings file yade_agent_batch_installer_settings.xml
and have assigned the XSD schema http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd.
The XML file contains a basic example with recommended values for an Agent installation (of only one Agent).
Each installation makes use of a profile in the YADE configuration 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>
Please follow these steps:
- Add a
<ProtocolFragments>
element and nodes for each host that you want to install the Agent for. - Add a
<Profile>
element and nodes for each host that you want to install the Agent for. - 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.
An example for the Batch Installer configuration file for the installation of two Agents might look like this:
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="utf-8"?> <Configurations xsi:noNamespaceSchemaLocation="http://www.sos-berlin.com/schema/yade/YADE_configuration_v1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Fragments> <ProtocolFragments> <SFTPFragment name="SFTP_192.11.0.111:4445"> <Directory><![CDATA[C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory> </FileSpecSelection> </Selection> </SourceFileOptions> </CopySource> <CopyTarget> <CopyTargetFragmentRef> <SFTPFragmentRef ref="SFTP_192.11.0.111:4445" /> </CopyTargetFragmentRef> <Directory><![CDATA[/home/test/tmp/]]></Directory> </CopyTarget> </Copy> </Operation> </Profile> <Profile profile_id="192.11.0.95:4445"> <Operation> <Copy> <CopySource> <CopySourceFragmentRef> <LocalSource /> </CopySourceFragmentRef> <SourceFileOptions> <Selection> <FileSpecSelection> <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec> <BasicConnection> <Hostname><<Directory><![CDATA[192.11.0.111C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Hostname>Directory> </BasicConnection>FileSpecSelection> <SSHAuthentication> </Selection> <Account><![CDATA[test]]></Account> </SourceFileOptions> <AuthenticationMethodPassword> </CopySource> <Password><![CDATA[xxxx]]></Password> <CopyTarget> </AuthenticationMethodPassword> </SSHAuthentication><CopyTargetFragmentRef> </SFTPFragment> <SFTPFragment<SFTPFragmentRef nameref="SFTP_192.11.0.95:4445" /> <BasicConnection> </CopyTargetFragmentRef> <Hostname>< <Directory><![CDATA[192.11.0.95/home/test/tmp/]]></Hostname>Directory> </BasicConnection>CopyTarget> <SSHAuthentication></Copy> <Account><![CDATA[test]]></Account></Operation> <AuthenticationMethodPassword></Profile> <Password><![CDATA[xxxx]]></Password> </AuthenticationMethodPassword> </SSHAuthentication> </SFTPFragment> </ProtocolFragments> </Fragments> <Profiles> <Profile profile_id="192.11.0.111:4445"> <Operation> <Copy> <CopySource> <CopySourceFragmentRef> <LocalSource /> </CopySourceFragmentRef> <SourceFileOptions> <Selection> </Profiles> </Configurations> |
Anchor | ||||
---|---|---|---|---|
|
Note that the file shown above is in the YADE XML format and that YADE versions 1.10 and older require a .ini
file to perform the transfer that is specified in the <globals><install_path><transfer><settings>
element in the Batch Installer configuration file.
- We recommended that you use the XML Editor to convert configuration files from XML to the
.ini
format (see the XML Editor for converting YADE configuration files (XML) into YADE setting files (.ini) section below for more information). - The following example shows as an example a
.ini
file that has been converted from the XML file above. You can download the example using this link: yade_agent_batch_installer_settings.ini.
Code Block | ||||
---|---|---|---|---|
| ||||
[protocol_fragment_sftp@SFTP_192.11.0.111:4445] protocol <FileSpecSelection> = sftp host <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec> <Directory><![CDATA[C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory> = 192.11.0.111 user </FileSpecSelection> </Selection> = test ssh_auth_method </SourceFileOptions> </CopySource> = password password <CopyTarget> <CopyTargetFragmentRef> <SFTPFragmentRef ref="SFTP= xxxx [protocol_fragment_sftp@SFTP_192.11.0.11195:4445" />] protocol </CopyTargetFragmentRef> <Directory><![CDATA[/home/test/tmp/]]></Directory> = sftp host </CopyTarget> </Copy> </Operation> </Profile> <Profile profile_id=" 192.11.0.95:4445"> user <Operation> <Copy> <CopySource> = test ssh_auth_method <CopySourceFragmentRef> <LocalSource /> = password password </CopySourceFragmentRef> <SourceFileOptions> = xxxx [192.11.0.111:4445] operation <Selection> <FileSpecSelection> = copy source_protocol <FileSpec><![CDATA[.*\.(sh|gz)$]]></FileSpec> = local file_spec <Directory><![CDATA[C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer]]></Directory> </FileSpecSelection> = .*\.(sh|gz)$ source_dir </Selection> </SourceFileOptions> = C:\Program </CopySource> Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer target_include <CopyTarget> <CopyTargetFragmentRef> <SFTPFragmentRef ref="SFTP= protocol_fragment_sftp@SFTP_192.11.0.95111:4445" /> target_dir </CopyTargetFragmentRef> = <Directory><![CDATA[/home/test/tmp/]]></Directory> [192.11.0.95:4445] operation </CopyTarget> </Copy> </Operation> </Profile> </Profiles> </Configurations> |
Note that this is an XML file and YADE will expect an .ini file to perform the transfer that is specified with the Batch Installer configuration file in the section <globals><install_path><transfer><settings>
.
...
Code Block | ||||
---|---|---|---|---|
| ||||
[protocol_fragment_sftp@SFTP_192.11.0.111:4445] protocol = copy source_protocol = local file_spec = .*\.(sh|gz)$ source_dir = sftp host C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer target_include = protocol_fragment_sftp@SFTP_192.11.0.111 user 95:4445 target_dir = test ssh_auth_method = password password = xxxx [protocol_fragment_sftp@SFTP_192.11.0.95:4445] protocol = sftp host = 192.11.0.95 user = test ssh_auth_method = password password /home/test/tmp/ |
Anchor | ||||
---|---|---|---|---|
|
We assume that you have opened the Batch Installer configuration file batch_installer_config_file.xml
in the XML Editor and assigned the scheduler_universal_agent_installations.xsd
XSD schema.
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.
The following configuration steps should be carried out:
- 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 forsudo
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
<installation_file>
element. This filename contains the version of the Agent which you are installing and it is helpful for recognizing the version of the Agents that are installed.- 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
- Specify the
- 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
- Agent options:
Info | ||
---|---|---|
| ||
|
The Batch Installer configuration file for the example can be downloaded here: batch_installer_config_file.xml and its contents are listed in the following code block:
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 = xxxx [192.11.0.111:4445] operationFiles (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer\yade_agent_batch_installer_settings.ini</settings> </transfer> <ssh> <user>test</user> = copy source_protocol<password>xxxx</password> <sudo_password>xxxx</sudo_password> = local file_spec <auth_method>password</auth_method> <port>22</port> </ssh> = .*\.(sh|gz)$ source_dir <installation_file>jobscheduler_unix_universal_agent.1.10.2.tar.gz</installation_file> <postprocessing> <command>echo ${ssh.sudo_password} | sudo -S = C:\Program Files (x86)\sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer target_includecp ${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 = protocol_fragment_sftp@SFTP_192.11.0.111:4445 target_dir update-rc.d jobscheduler_agent_${agent_options.scheduler_http_port} defaults</command> </postprocessing> </globals> <installation = /home/test/tmp/ [192.11.0.95:4445] operationlastRun="2015-11-20 14:11"> <agent_options> <scheduler_user>test</scheduler_user> = copy source_protocol <scheduler_log_dir>/var/log/sos-berlin.com/jobscheduler/agent</scheduler_log_dir> </agent_options> <ssh> = local file_spec <host>xxxx</host> </ssh> </installation> <installation lastRun="2015-11-20 14:11"> = .*\.(sh|gz)$ source_dir <agent_options> <scheduler_user>test</scheduler_user> = C:\Program Files (x86)\ <scheduler_log_dir>/var/log/sos-berlin.com\jobscheduler\vg_4444\scheduler_data\config\batch_installer target_include/jobscheduler/agent</scheduler_log_dir> = protocol_fragment_sftp@SFTP_192.11.0.95:4445 target_dir</agent_options> <ssh> <host>xxxx</host> = /home/test/tmp/</ssh> </installation> </installations> |
Info | ||
---|---|---|
| ||
|
Excerpt |
---|
The XML Editor can be used to manage the Batch Installer configuration file and the YADE configuration file. XML Editor for Batch Installer configuration fileAn example |
Batch Installer configuration file |
for the installation of a single Agent is shown in the following screenshot: |
XML Editor for YADE configuration fileAn example |
YADE configuration file |
for the installation of a single Agent is shown in the next screenshot: |
|
The "YADE Xml2Ini Converter" function in the XML Editor is available for converting YADE files from |
XML |
to |
the |
format required by versions of YADE before 1.11. Clicking on the button of the same name will open the following form: |
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 |
format. A pop-up window will show every time a change is saved |
if the option "Show notification on autotransform" is chosen. |
|