This page provides requirements, permissions, and steps to install the Machine Agent.
Make sure to thoroughly test your deployment in a staging or test environment before deploying it to production.
To avoid permission issues, install the agent as the same user who owns the Machine Agent files or as an administrator on the host machine.
<machine-agent-home>installation directory should be readable by the Machine Agent.
confdirectory in the agent installation directory.
<machine_agent_home>). Appdynamics recommends that you restrict permissions to users authorized to start, stop, and configure the Machine Agent:
The following table lists characters that are not supported for the
<machine-agent-home> directory name or in any directory in the path:
Not Supported on any OS
Not Supported on Linux
Not Supported on Windows
|Whitespace characters||% #||% # \ / : * ? " < > ||
|An exclamation point at the end of the directory name||Control characters such as ASCII EOL, CR, etc.|
controller-info.xml file contains the properties used to specify agent to Controller communications. To specify the Controller host, port, and account access key properties, see Plan the Machine Agent Configuration.
Based on your installation requirements, you may need to configure additional properties.
The following steps are for new installations. To upgrade version 4.3 and earlier, see Upgrade the Standalone Machine Agent.
From AppDynamics Downloads, download the Machine Agent installation package for your OS environment onto the machine you want to monitor.
If there is no download bundle for your OS, use the Machine Agent zip file without the JRE, and use a separately downloaded JRE to run it. You need to download a separate JRE if the one already installed on the machine is a version earlier than JRE 1.8.
Verify the Standalone Machine Agent Installation
Start the Machine Agent by executing
<machine_agent_home>/bin/machine-agent. If you have
system properties, you can add them to the end of the command. To review machine usage, enter