On this page:
This topic describes upgrading an existing installation of the Machine Agent. The instructions have been tested and certified to work for Machine Agent versions 4.3 and above.
For a new installation, see Install the Standalone Machine Agent.
AppDynamics recommends using version 4.3, or later, of the Machine Agent for this release. Version 4.1, or earlier, is no longer supported. Although Machine Agents may be compatible with future releases of the Controller, AppDynamics only provides support for Machine Agent versions with the Controller for two years after the release of the agent.
<machine_agent_home>directory to a
<machine_agent_home_BACKUP>so you can revert to the previous installation if required.
<machine-agent-home>/monitors/analytics-agent/conf/watermarkAnalytics Agent location:
<machine-agent-home>/monitors/analytics-agent/conf/jobAnalytics Agent location: <analytics-agent-home>/conf/job
<machine_agent_home>that you want to upgrade. See Start and Stop the Standalone Machine Agent.
sudo rpm -U <package>
For all other scenarios:
First, delete the
<machine_agent_home> for the old agent. Make sure you retain the
<machine_agent_home_BACKUP> you created in step 1.
Then install the Machine Agent as described for your specific installation in Install the Standalone Machine Agent.
If you are running the Analytics Agent as an extension to the Machine Agent, failure to clear out the old directory or use a new location may cause your embedded Analytics Agent to fail to start.
Configure the agent settings in
/conf/controller-info.xml. See Standalone Machine Agent Configuration Properties.
The RPM-based Linux installer retains the configuration settings for the previous agent by default.
If you used another installer and want to maintain your previous agent configuration, copy the
.vbsfiles (VbScript) and delete the
.cmdfiles (Windows Command Script), which are left over from your previous version.