...
The Batch Installer solution is available for the installation and update of the JobScheduler Universal Agent. The Batch Installer It allows installation of any number of Agents on multiple servers across a range of environments.
Article Scope
A general This article provides a detailed description of the configuration and use of this solution. installation of the JobScheduler Universal Agent can be found in the JobScheduler Universal Agent - Installation & Operation article.
In addition, a number of "How to ..." articles are available describing the use of the Batch Installer in different environments. These are linked from the JobScheduler Universal Agent - Batch Installation - Use Casesand Update of Agents article.
This article contains reference information for users seeking more detailed information than provided in the batch installation in different environments articles.
Feature Availability
Display feature availability | ||
---|---|---|
|
...
The AgentBatchInstaller
job is responsible for creating the JobScheduler orders for the job chain. Each of these orders is named according to the pattern <host>:<port>
to convey the host and port of the server where each Agent is to be installed.
The Universal Agent Batch Installer Job Chain
The universal_agent_installer
job chain has four job nodes configured in series as follows:
Download the Batch Installer and Agent Files
Windows and Unix versions of the Batch Installer can be downloaded from the SOS Downloads page along with the appropriate Agent version.
...
shown in the code block and diagram below:
Job Chain: universal_agent_installer.job_chain.xml
...
Code Block |
---|
...
Code Block | ||||
---|---|---|---|---|
| ||||
<job_chain name="universal_agent_installer"> <job_chain_node state="CheckPreRequisite" job="CheckPreRequisite" next_state="Sync" error_state="error"/> <job_chain_node state="Sync" job="Sync" next_state="TransferInstallationSetup" error_state="error"/> <job_chain_node state="TransferInstallationSetup" job="TransferInstallationSetup" next_state="PerformInstall" error_state="error"/> <job_chain_node state="PerformInstall" job="PerformInstall" next_state="success" error_state="error" on_error="suspend"/> <job_chain_node state="success"/> <job_chain_node state="error"/> </job_chain> |
...
- You can define defaults for all elements in the <
globals>
element. - You can use variables for values e.g.
${ssh.host}
. - It is recommended that you specify the name of the YADE settings file in the <
globals>
element and use the default profile name as shown in the example Configuration File below. This will mean that it is not necessary to define<installation><transfer>
elements.
...
Code Block | ||
---|---|---|
| ||
<command>echo ${ssh.sudo_password} | sudo cp ${install_path}/bin/jobscheduler_agent.sh /etc/init.d/jobscheduler</command> |
Anchor | ||||
---|---|---|---|---|
|
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.
...