| Table of Contents |
|---|
Introduction
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 an environment where Agents have already been installed. 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 Agent Batch Installer for 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 additional Agent installation will overwrite the previous Agent installation.
- The new Agent(s) will be operated with the same user and installation path as 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.
The example described below use case described in this article builds on the example case presented in the Batch Installation - Use Cases - Multiple Instances article in which a total of four agents were installed on two servers. Note, however, that only one Agent server with a single Agent installed on it is required before the current example can be implemented.
...