This page provides requirements, permissions, and steps to install the standalone Machine Agent.
Make sure to thoroughly test your deployment in a staging or test environment before deploying it to production.
- JRE 1.8 is required.
- In 4.2, JRE 1.8 is bundled with the OS-specific Machine Agent installation downloads.
- The Machine Agent starts within its own JVM.
- You can use an existing JRE previously installed in your environment.
Installation Directory and Path Name Requirements
The following table lists characters that are not supported for the
<machine-agent-home> directory name or in any directory in the path:
|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.
Installation for New Standalone Machine Agent
The following steps are for new installations. To upgrade version 4.3 and earlier, see Upgrade the Standalone Machine Agent.
- Plan the Machine Agent Configuration.
From the From AppDynamics Downloads Portal, 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