You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
0 rates

This topic describes upgrading an existing installation of the Machine Agent versions 4.3 and above.  

For a new installation, see Install the Standalone Machine Agent

4.3 or later version of Machine Agent Recommended

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.

Perform the Upgrade

  1. Do the following (as needed) before you update the agent: 
    1. Review the Release Notes for changes that affect your environment.
    2. Back up the <machine_agent_home> directory to a <machine_agent_home_BACKUP> so you can revert to the previous installation if required. 
    3. If you are upgrading the Controller as well as the agents: Upgrade the Controller Using the Enterprise Console and then return to this procedure.
    4. If you have been collecting Log Analytics data by running the Analytics Agent via the Machine Agent: Do the following.
      1. Preserve the old watermark file so that you can copy it to the new <analytics-agent-home>.
              Machine Agent location: <machine-agent-home>/monitors/analytics-agent/conf/watermark
              Analytics Agent location: <analytics-agent-home>/conf/watermark 
      2. Preserve your pre-existing job files so that you can copy them to the new <analytics-agent-home>.
               Machine Agent location:  <machine-agent-home>/monitors/analytics-agent/conf/job
               Analytics Agent location: <analytics-agent-home>/conf/job
  2. Download the installer suitable for your OS environment from the AppDynamics Download Center (https://appdynamics.com/download).
  3. Stop all instances of the Standalone Machine Agent that are currently running from the <machine_agent_home> that you want to upgrade. See Start and Stop the Standalone Machine Agent
  4. Update your Machine Agent installation as follows:
      • RPM-based Linux installation: 
        Update the existing package. For example: 
                  sudo rpm -U <package>
      • RPM-based installation on a systemd Linux system (such as CentOS 7, Ubuntu, newer Fedora Core systems, newer OpenSUSE systems, and newer SUSE Enterprise Linux systems): 
        If you don't know if your Linux installation is using systemd, do a clean install to avoid issues: remove the old package and then install the new one. 
      • 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.  

  5. Configure the agent settings in <machine_agent_home>/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 <machine_agent_home_BACKUP>/conf/controller-info.xml file to the new installation directory.

     

  6. Do the following (as needed) before you start the updated agent.
    1. If you are updating on Windows: When you install the new Machine Agent in the existing directory, you may see two "InstallService" and "UninstallService" files. Use the .vbs files (VbScript) and delete the .cmd files (Windows Command Script), which are left over from your previous version.
    2. If the agent install package includes a new JRE: Update any related custom scripts that use the Machine Agent JRE.
    3. Update all users who have the Account Administrator role for the account add the appropriate SIM roles (SIM admin and SIM user) to other users in the account as needed.
  7. Start the agent, verify the agent installation, and verify that the agent is reporting to the Controller as described for your specific installation in Install the Standalone Machine Agent.
  • No labels