Agent Installation

You can install agents on supported operating systems using an interactive installer, a silent installer, or manual installation steps.

For production environments, Serena recommends creating a user account dedicated to running the agent on the machine where the agent is installed.

For simple evaluations, the administrative user can run the agent on the machine where the server is located. If you plan to run deployments on several machines, a separate agent should be installed on each machine. If, for example, your testing environment consists of three machines, install an agent on each one. Follow the same procedure for each environment the application uses.

Important: Except for evaluation purposes, do not install an agent on the same machine as the server.

Each agent needs the appropriate rights to communicate with the Release Automation server.

At a minimum, each agent should have permission to:

Create a cache. By default, the cache is located in the home directory of the user running the agent. The cache can be moved or disabled.
Open a TCP connection. The agent uses a TCP connection to communicate with the server's JMS port.
Open a HTTP(S) connection. The agent must be able to connect to the Release Automation user interface in order to download artifacts from the CodeStation repository.
Access the file system. Many agents need read/write permissions to items on the file system.

Note: For UNIX environments, you can install agents remotely from the Release Automation web application. Agents installed remotely cannot be run as a service. See Installing Agents Remotely.

The following topics lead you through an agent installation.

Agent Installation

Related Topics