On this page:
The AppDynamics Universal Agent runs on each app server machine where you want to deploy runtime agents. The first step in using the Universal Agent to manage your agent deployment, therefore, is installing the Universal Agent on the monitored machines.
This topic introduces Universal Agent installation. When you are ready to install the Universal Agent, see the topic specific to your operating system:
The Universal Agent occupies about 20 MB of disk space. When you start the installation, the script first checks the system for sufficient space. Using the Universal Agent to add more runtime agents to your target machine later will require additional space.
The installation process installs the Universal Agent as an automatically started system service. Therefore, you need to perform the installation on the system as a user with sufficient privileges for this type of installation. On Linux, for example, you typically need to run the script as a user with sudo privileges. See Permissions for Running the Universal Agent.
The Universal Agent can support the deployment and management of the following runtime agents:
Supported environments and requirements for the runtime agents still apply even when they are being managed by the Universal Agent. For example, in 4.4, the Network Agent is only available on Linux. Be sure to review the requirements for each runtime agent.
Some Universal Agent features (such as automatic JVM attachment and dynamic rulebook value propagation) have additional requirements and limitations, which are discussed in separate topics.
The Universal Agent is available on the following Linux and Windows versions:
Installing the Universal Agent on Windows requires the Universal C Runtime. If it is not installed on your Windows server you should install the Update for Universal C Runtime in Windows.
Universal Agent is supported on:
Installing the Universal Agent on Linux requires the GNU C Library version 2.12, commonly known as glibc 2.12. The minimum versions of the common distributions that meet this requirement are:
The initial configuration for the Universal Agent specifies the Controller host, port, account name and account key, so you will need to know the values to use before starting. These settings are equivalent to those used by other types of agent. You can find out more in the Agent-to-Controller Connections topic. Note that, on Linux, if you acquire the Universal Agent from the Controller, the settings are preconfigured.
After initial installation, you can update new versions of the Universal Agent itself using the Universal Agent rulebook. For more information, see Universal Agent Rules.