Date: Thu, 28 Mar 2024 17:05:04 +0000 (UTC)
Message-ID: <1605267538.11757.1711645504874@change.sos-berlin.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_11756_573905111.1711645504873"
------=_Part_11756_573905111.1711645504873
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Scope
- The Agent Batch Installer provides a solution that:
- deploys JobScheduler Universal Agents
- and allows the installation or update of any number of Agents on multip=
le servers.
- The Agent Batch Installer is used for deploying Agents to Unix systems.=
It is not available for Windows systems for the following reasons:
- The JobScheduler Master transfers the files needed for deployment to th=
e Agent servers using SSH:
- Windows standard installations do not come with an SSH server. This mea=
ns that additional software would have to be installed on every Agent serve=
r just for performing the file transfer.
- Note that this only applies for the Agent servers. If the JobScheduler =
Master is running on a Windows machine, this solution can still be used for=
deploying the Agents from there to Unix servers.
- Most Windows administrators work already with other more complex tools =
to deploy software on Windows machines (deployment tools such as SCCM), whe=
reas for Unix the deployment tools are not that complex and it makes sense =
to offer such a tool for them.
- The Agent Batch Installer solutio=
n can be downloaded from http://www.sos-berlin.com/jobscheduler-downloads, see "Universal Agent Batch Installer"=
.
- The Batch Installer supports:
- First Installation: an Agent has not yet been installed on the server.<=
/li>
- Update Installation: an Agent has already been installed and may be up =
and running.
- Note that the Batch Installer is only available for the current JobSche=
duler Universal Agent version.
The Batch Installer Application
The Batch Installer is made up from a Job Chain and configuration files =
that allow a JobScheduler Master to:
- connect to the Server(s) that the Agent(s) are to be installed on,
- transfer the files required for the installation(s) and
- execute the required Agent installation(s).
The Batch Installer application has two main components:
- a JobScheduler
AgentBatchInstaller
job
- a JobScheduler
universal_agent_installer
job cha=
in.
In addition, two XML configuration files are needed for the application:=
batch_installer_config_file.xml
and
yade_agent_batch_installer_settings.xml
The AgentBatchInstaller
job is a standalone job t=
hat is responsible for creating the JobScheduler orders for the =
universal_agent_installer
job chain. Each of these orders is na=
med according to the pattern <host>:<port>
&nb=
sp;to convey the host and port of the server where each Agent is to be inst=
alled.
The universal_agent_installer<=
/code> job chain
The universal_agent_installer
job chain has =
four job nodes configured in series as follows:
The individual nodes in the job chain have the following functions:
CheckPreRequisite
- Check for the correct Java version
- Check whether a JobScheduler Universal Agent already has been installed=
.
- If yes, then the Installer:
- shuts down any instances that are possibly running
- removes the installation
Sync:
Wait until all prerequisites have been checked and a=
ll instances shut down. FEATURE AVAILABILITY ENDING WITH RELEASE 1.12
TransferInstallationSetup
: Transfers the installer files t=
o the host
PerformInstall
: Starts the installation using SSH.
- The step before transferred installation script will be executed
- The installation script installs and starts the JobScheduler Universal =
Agent
- Finally the post-processing commands will be executed
- The post-processing commands are specified with the
<installat=
ion><postprocessing><command> element
- Three commands will be executed:
- if you require additional commands, please add the call in the
Pe=
rformInstall
job
- The default commands set up the autostart for JobScheduler Universal Ag=
ent on a Linux server (Ubuntu distribution)
echo ${ssh.sudo_password} | sudo -S cp ${install_path}/bin/jobsch=
eduler_agent.sh /etc/init.d/jobscheduler
echo ${ssh.sudo_password} | sudo -S update-rc.d jobscheduler defa=
ults
Installation Tutorial
The Batch Installation Tutorial - Installation=
of a single Universal Agent article provides a step-by-step guide to t=
he configuration of the Batch Installer and is recommended as a starting po=
int.
Installation Use Cases
The following articles describe the procedure for using the Batch Instal=
ler to install and update JobScheduler Universal Agents for a number of use=
cases:
- Batch Installation - Use Cases - Homogeneous environment:&nb=
sp;We define a homogeneous environment as one in which a number of JobSched=
uler Agents will be installed according to the same prerequisites:
- A JobScheduler Master is up and running.
- The Agent installations are to be performed on any number of servers th=
at have the same operating system. One Agent is to be installed per se=
rver.
- The Agents will be operated with the same user, listening port and inst=
allation path.
- Batch Installation - Use Cases - Heterogeneous environment=
: We define a heterogeneous environment as one in which a number of Jo=
bScheduler Agents will be installed according to different prerequisites:
- A JobScheduler Master is up and running.
- The Agent installations are to be performed on any number of servers th=
at are not required to have the same operating system. One Agent is to=
be installed per server.
- The Agents will be operated with different accounts, listening ports an=
d installation paths.
- Batch Installation - Use Cases - Multiple Instances: A numbe=
r of JobScheduler Agents will be installed on each server and each installa=
tion will be based on different prerequisites:
- A JobScheduler Master is up and running.
- The Agent installations are to be performed on any number of servers th=
at are not required to have the same operating system. More than one A=
gent is to be installed per server.
- On every Agent server the Agents will be operated with different accoun=
ts and different listening ports.
- The Agents will be operated with different accounts (within the same Ag=
ent server) to make the example more multifaceted, although the same user c=
an operate more than one Agent if the Agents run on different ports.
- The installation path will be the same for all Agent installations.
- Batch Installation - Use Cases - Reuse of B=
atch Installer Configuration Files: Installing JobScheduler =
Agents in an environment in which a number of the Agents have already been =
installed and where the new Agents are to be installed on a server which al=
ready has at least one Agent. The environment can be summarized as having t=
he following characteristics:
- A JobScheduler Master is up and running.
- A number of JobScheduler Agents have already been installed on differen=
t Agent servers.
- At least one additional Agent is to be installed on a server which alre=
ady has an Agent installed on it.
- The additional Agent installation=
will overwrite the previous Agent installation.
- The new Agent(s) will be operated with the same account and installatio=
n path as at least one of the Agents already installed on an Agent server.<=
br>
The new Agent will be identified by its listening port which will be unique=
for the server which the Agent is being installed on.
Reference Documentation
For detailed information not contained in the installation use case arti=
cles described above, covering:
- the Jobs, Job Parameters and Job Chains used for the Agent Batch Instal=
ler,
- customizing the Jobs, Job Chains and the configuration files required f=
or the Agent Batch Installer.
Please refer to the article Batch Installation - Reference Documentation=
.
------=_Part_11756_573905111.1711645504873--