This section provides instructions and recommendations for installing Deployment Automation agents.
Install at least one agent for a basic installation. Use one of the following methods:
|Interactive installation||See Install agents with the interactive installer.|
Windows: See Install agents in silent mode on Windows.
UNIX/Linux: See Install agents in silent mode on UNIX/Linux.
|Command-prompt installation||See Install agents from a command prompt.|
The Windows agent installer uses a standard distribution technique of the JRE that redistributes the Java runtime files in accordance with Java standards. This creates a private JRE instance that doesn't interfere with other installed Java applications.
But if you create references to the Java files that are installed by the agent, or if you interfere with the agent's private installation directory, you may corrupt other existing Java applications on the host machine.
Download and install a Solaris JRE 8 before running the agent installer. To run the installer, specify the path to the JRE:
|z/OS||To install a z/OS agent, see Install and configure the z/OS agent.|
Guidelines for installing or upgrading agents:
|Install multiple agents on multiple machines||
If you plan to run deployments on several machines, install a separate agent with a unique name on each machine. For example, if your testing environment consists of three machines, install an agent on each one.
Follow the same procedure for each environment the application uses.
|Install multiple agents on one machine||If you plan to install multiple agents on a single machine, make sure that all names are unique: installation directory name, agent name, and service name, if running the agent as a service.|
|Install agents remotely||UNIX: You can install agents remotely through the user interface. See (UNIX) Install agents remotely.|
|Upgrade agents||Agents are upgraded through the user interface. See Upgrade agents.|
|Uninstall agents||Windows and UNIX/Linux: See Upgrade agents.|
Before you can use an agent, verify that it is assigned to an active license. For details, see Manage licenses.