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>). It is good practice to restrict permissions to users authorized to start, stop, and configure the Machine Agent:
<machine-agent-home>\bin\machine-agent.vbs(if running as a terminal application)
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||% #||% # \ / : * ? " < > ||
|Exclamation point at the end of the directory name||Control characters such as ASCII EOL, CR, etc.|
controller-info.xml file contains the properties for specifying agent to Controller communications. You will need to specify the Controller host, port, and account access key properties. See Plan the Machine Agent Configuration for more details. You might need to configure additional properties depending on your install requirements.
The following steps are for new installations.
Follow these general steps to complete your installation:
Step 1: Plan the Machine Agent Configuration. Don't skip this step, there are a number of things to consider when configuring the Machine Agent.
Step 2: Download the Machine Agent installation package for your OS environment from the AppDynamics Download Center (https://appdynamics.com/download) and install it on 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 below JRE 1.7.
Install Using the Non-JRE Zip File - use this for OS environments other than Linux, Solaris, Windows, and Mac OS X
Step 4: Start the Machine Agent by executing
<machine_agent_home>/bin/machine-agent. If you have java or system properties, you can add them to the end of the command. To see usage, enter
For full-screen viewing, click Start Monitoring Servers.