...
- for installing and updating JobScheduler Universal Agents.
- which allows the installation or update of any number of Agents on multiple Agent servers.
Use Cases
The following articles describe the diverse Use Cases a user could face regarding an installation or a number of use cases regarding the installation and update of JobScheduler Agents and how to use the Agent Batch Installer solution in each case:
| Excerpt |
|---|
- Batch Installer Installation - Use Cases - Homogeneous environment: We define a homogeneous environment as one in which a number of JobScheduler 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 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.
- Batch Installer Use Case: Heterogeneous environmentsInstallation - Use Cases - Heterogeneous environment: We define a heterogeneous environment as one in which a number of JobScheduler 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 that do are not have required to have the same operating system. One Agent is to be installed per server.
- The Agents will be operated with different usersaccounts, listening ports and installation paths.
- Batch Installer Installation - Use Case Cases - Multiple Instances: A multiple number of JobScheduler Agents will be installed on every Agent each server and every each installation 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 that do are not have required to have the same operating system. More than one Agent is to be installed per server.
- In On every Agent server , the Agents will be operated with different users accounts and different listening ports.
- The Agents will be operated with different users accounts (within the same Agent server) to make the example more multifaceted, although the same user can 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 - Additional Installations: 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 already has at least one Agent. The environment can be summarized as having the following characteristics:
- A JobScheduler Master is up and running.
- A number of JobScheduler Agents have already been installed on different Agent servers.
- At least one additional Agent is to be installed on a server which already has an Agent installed on it.
- The new Agent(s) will be operated with the same user account and installation path as at least one of the Agents already installed on an Agent server.
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 any detailed information about:
- Jobs, job parameters and job chains used for the Agent Batch Installer
- Customizing the jobs, job chains and the configuration files needed for the Agent Batch Installer to work
please have a look at refer to the article Batch Installation - Reference Documentation.
...