On this page:
This topic describes upgrading when you have a pre-4.3 version of the Machine Agent installed.
For a new installation, see Install the Standalone Machine Agent.
To consolidate pre-4.2 installations with multiple machine agents on one server, see Consolidate Multiple Machine Agents.
4.2 (or higher) version of Machine Agent Recommended
AppDynamics recommends using version 4.2 (or higher) of the Standalone Machine Agent for this release. You cannot use version 4.1 (or earlier) on any machine that has a Server Visibility license.
<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 Property Reference.
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
<machine_agent_home_BACKUP>/conf/controller-info.xml file to the new installation directory.
.vbsfiles (VbScript) and delete the
.cmdfiles (Windows Command Script), which are left over from your previous version.