Discussion Feed

A complete checklist for upgrading platform components   NOTE: The information in this article is not release-specific. You can reference it for any release. To make sure you complete all the tasks necessary for upgrading platform components after a release, we recommend following the upgrade checklist instructions below.    Table of Contents Prepare to upgrade your platform components Plan your platform component upgrade  Step 1: Upgrade the Enterprise Console Step 2: Upgrade the Events Service Single-node install or manual upgrade? Step 3: Upgrade the EUM Server Step 4: Back up the Controller Step 5: Upgrade the Controller with the Enterprise Console Troubleshooting Additional Resources   Prepare to upgrade your platform components Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of your AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your platform component  upgrade Before upgrading to a newer version of the platform, complete the tasks outlined in the Update Product Components  documentation. To ensure all data is transferred properly, perform your upgrades in the specific recommended order for the components you’re using:   Step 1. Upgrade the Enterprise Console Start with a review of the Upgrade the Enterprise Console documentation.   To determine the requirements, review the Controller system requirements and increase your hardware resources if necessary.   Step 2. Upgrade the Events Service   Do I need a single node install or a manual upgrade? The Enterprise Console supports the installation of the Events Service on a Windows environment for a single node install . If you have several remote nodes, you will need to do a manual upgrade of the Events Service cluster and set the keys manually. For instructions on connecting to the Events Service, see the End-User Monitoring Connection Settings  documentation.   Note: Even though th e Enterprise Console will set and sync the keys between the Controller and Events Service, we still recommend confirming that the keys were synced correctly: appdynamics.on.premise.event.service.key == ad.accountmanager.key.controller Note: If you're upgrading the Events Service using the Enterprise Console, you don't need to stop the Events Service.   Complete the Events Service upgrade Follow the Upgrade the Events Service documentation to complete the Events Service upgrade.   Step 3. Upgrade the EUM Server See Upgrade the EUM Server for instructions on upgrading an EUM Server.   Step 4. Back up the Controller Complete a full backup of the Controller. Refer to  Back up the Existing Controller for instructions.   Step 5. Upgrade the Controller with the Enterprise Console   Final Upgrade Considerations Before completing the upgrade process, review the following and implement as appropriate:   Upgrading an HA Pair If you're upgrading an HA pair, we recommend upgrading via CLI using the phased upgrade method (new in v4.5.6) . This allows you to retain the Controllers' HA roles so that the primary and secondary roles do not switch after the upgrade.   You can also check the status of your primary Controller before upgrading the secondary.  If you encounter any issues during or post-upgrade, you can roll back by promoting and failing over to the preserved, secondary Controller.    Though we recommend the phased upgrade method, it is also possible to use GUI or the old CLI method to upgrade your HA pair.   Upgrading from a small to an extra-large deployment You can directly upgrade from small/demo deployments to large/extra large deployments. See the Tuning for Large Profile Controller documentation for instructions on preparing a large deployment.   Be sure to check the Controller’s database.log Check the Controller&rs database.log for any errors during this process. You can find the log at <controller_home>/db/logs/database.log> . There should not be any InnoDB: Error lines in the log from the last startup. If any errors are found, contact AppDynamics Support before attempting the upgrade. Upgrading the Controller with a corrupt database may put the Controller in a bad state with a high recovery time.   Upgrade the Controller with the Enterprise Console Once you’ve resolved the preceding considerations and completed the outlined steps, refer to the Upgrade the Controller using the Enterprise Console  documentation to perform and complete the upgrade.   Troubleshooting In the event of an error condition, follow the troubleshooting steps in the Troubleshoot the Upgrade documentation.  If you experience an error condition when upgrading a platform component, please go to  www.appdynamics.com/support, scroll to the AppDynamics Support section, and click Support Portal.         Additional Resources How do I get started with upgrading my AppDynamics components? ... View more

A complete checklist and compatibility matrices for Controller, Agents, and platform components   NOTE: The information in this article is not release-specific. You can reference it for any release.   Before you upgrade your Controller, you’ll want to be familiar with how the new Controller version you’re targeting interacts with the Agents in your environment.    How does the version compatibility for Controllers and component agents map to your environment? Are there interim versions you need to consider? Do you know where to find reference information and instructions so you can upgrade those components successfully?   To make sure you know the steps to follow for a successful release upgrade, we recommend starting with this article and then following the instructions in our upgrade checklists (links available below).   Table of Contents Things to do before you begin: Review Product Announcements and Alerts  Review Agent-to-Controller version compatibility grids  Database Agent-to-Controller Version Compatibility  Other Compatibility Considerations:   On-premises Compatibility Agent Backward Compatibility  How do you determine your Controller version? Next Steps: Checklists for upgrading each component      Before you begin, be sure to conduct a review Before upgrading any component, we recommend you review available information about version compatibility between the target Controller and all the Agents relevant to your environment:   ✓ Product Announcements and Alerts ✓ Version Compatibility Matrices ✓ Compendium of Upgrade Checklist Articles   Review Product Announcements and Alerts Review the Product Announcements and Alerts page to discover and understand the details of upgrading any intermediate versions between your current Controller version and the one you’re targeting.   Review Agent-to-Controller version compatibility grids Review the Agent-to-Controller and Database Agent-to-Controller compatibility grids below for various components of the AppDynamics environment.    NOTE : For complete details about component compatibility, see our Community and technical documentation .   AGENTS SUPPORTED  CONTROLLER  VERSIONS v4.3 v4.4 v4.5 v20.3 - future releases Analytics The Analytics Agent’s version should be: less than or equal to the Controller’s version and also less than or equal to the Event Service version Apache Web Server The Apache Web Server Agent’s version should be less than or equal to the Controller’s version Java 4.x - 4.3 4.4.1 - 20.x (1) 4.5 - 20.x  (1)  4.4 - 20.x  (1)(2) JavaScript (ADRUM)  The JavaScript Agent’s (ADRUM) version should be less than or equal to the EUM Server version Machine 4.x - 4.3 4.4.1 - 20.x  (1) 4.5 - 20.x  (1) 4.4 - 20.x ( 1)(2) .NET 4.x - 4.3 4.4.1 - 20.x  (1) 4.5 - 20.x  (1) 4.4 - 20.x  (1)(2) (1) Controller version supports through the most recent released Agent version (2) Controller version does not support Agent version 4.1   Database Agent-to-Controller Version Compatibility   NOTE : The AppDynamics DB Agent isn’t backward compatible. Its version should be less than or equal to the Controller version.   Supp SUPPORTED CONTROLLER VERSIONS v4.3 v4.4 v4.5 v20.3 -future releases DB Agent 4.1-4.3 (1) 4.1-4.4  (1) 4.1-4.5  (1) 4.1 - 20.x (1)(2) (1) Controller version supports through the most recently released Database Agent version (2)  DB Agent is only compatible up to its corresponding Controller version   Other compatibility considerations On-premises compatibility Things to keep in mind when you have an on-premises deployment:   The Controller version should be less than or equal to the EUM Server version, and should also be less than or equal to Events Service version The EUM Server version should be less than or equal to the Events Service version The Java Script Agent version should be less than or equal to the EUM Server's version   Agent backward compatibility Starting with release v.4.5x, backward compatibility is supported on the following agents: Java .NET Node.js PHP Python Go SDK C/C++ Machine   How do you determine your Controller version? On your Controller’s Home page, click the Settings gear on the upper right. Then click About AppDynamics  above the logout option. Home > Overview > Settings > then click About AppDynamics   A dialog box with the Controller’s current version and build will appear. "About AppDynamics” dialog box, headed by the Controller version and build     Next Steps: Checklists for upgrading each component After following the recommendations in this article, refer to the relevant upgrade checklists for each type of AppDynamics component:    NOTE: These guides are not release-specific and can be referenced for any release.   How do I get started with upgrading platform components? How do I get started with upgrading Machine Agents? How do I get started with upgrading Java Agents? How do I get started with upgrading .NET Agents? How do I get started with upgrading dynamic language agents? How do I get started with upgrading Analytics Agents? How do I get started with upgrading Database Agents How do I get started with upgrading EUM servers, agents, and SDKs   Last Updated: 7/20/20 ... View more

To make sure you complete all the tasks necessary for upgrading your Dynamic Language Agents after a release, we recommend following the instructions below.   NOTE : The information in this article is not release-specific. You can reference it for any release   Table of Contents Prepare to upgrade your EUM servers, agents and SDKs Planning your EUM Server, Agent, and SDK upgrades  Plan your on-premises EUM server upgrade Plan your EUM agents and SDK upgrades How to upgrade your EUM Server, Agent, and SDK How do I upgrade my on-premises EUM Server?   How do I upgrade EUM Agents and SDKs?  Additional Resources   Prepare to upgrade your EUM servers, agents and SDKs Review the Product Announcements and Alerts page  for details on any intermediate versions between the current version of your instance and the version you are targeting. Review the compatibility matrix in our Community and documentation for various components of the AppDynamics environment. Review our EUM component compatibility article for details specific to EUM. Review the Mobile Agent Version and Deployment Support Matrix to determine the minimum versions of the Controller and EUM Server required for supporting the latest features of the Mobile Agents. For platforms where the Controller, EUM Server, and Events Service are being upgraded at the same time,  the Controller version should be less than or equal to (<=) the Events Service version and you should perform the upgrades in a specific order. See the  Upgrade Platform Components  documentation for details on the upgrade order. For example, the Events Service should be upgraded before the EUM server. This documentation also instructions for upgrading the Events Service .   Planning your upgrades Considerations for upgrading an on-premises EUM Server and EUM Agent and SDK are different. See each below.   Plan your on-premises EUM Server upgrade The EUM Server version should be less than or equal to (<=) the Events Service version Ensure the key matches between the Events Service, EUM Server, and Controller: analytics.accountAccessKey == ad.accountmanager.key.eum ==appdynamics.es.eum.key For instructions on configuring EUM connection settings, see:  Connect to the Events Service See Upgrade the Production EUM Server for step-by-step instructions. In addition to upgrading your server, you will need to follow the instructions on migrating your EUM data. For the v4.5 production EUM Server, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine.   After upgrading your EUM Server, you can upgrade your Controller following the steps outlined in Upgrade the Controller using the Enterprise Console .   Plan your EUM agent and SDK upgrades Before upgrading EUM Servers, Agents and SDKs, review the following: Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. for various components of the AppDynamics environment, review the compatibility matrix in the Knowledge Base article  How does EUM component compatibility work?, as well as the About Agent and Controller Compatibility section in the   Agent and Controller  documentation. Review our EUM component compatibility article for details specific to EUM. Review the Mobile Agent Version and Deployment Support Matrix to determine the minimum versions of the Controller and EUM Server required for supporting the latest features of the Mobile Agents for various components of the AppDynamics environment.   For platforms where the Controller, EUM Server, and Events Service are being upgraded at the same time , the Controller version should be lesser than or equal to (<=) the Events Service version. You must perform the upgrades in a specific order. For example, be sure to upgrade the Events Service before the EUM Server.   See Upgrade Platform Components for details on the upgrade order.    How to upgrade your EUM Server, Agent, and SDK See below for the considerations for upgrading your on-premises EUM Server, EUM Agent and SDK.   How do I upgrade my on-premises EUM Server? The EUM Server version should be less than or equal to (<=) the Events Service version Ensure the key matches between the Events Service, EUM Server, and Controller: analytics.accountAccessKey == ad.accountmanager.key.eum ==appdynamics.es.eum.key For instructions on configuring EUM connection settings, see: Connect to the Events Service See Upgrade the Production EUM Server for step-by-step instructions. In addition to upgrading your server, you will need to follow the instructions on migrating your EUM data. For the 4.5 production EUM Server, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine.   After upgrading your EUM Server, you can upgrade your Controller following the steps outlined in Upgrade the Controller using the Enterprise Console .   How do I upgrade EUM Agents and SDKs? Upgrade the JavaScript Agent Note: If you are a 4.4 SaaS customer and have an EUM license, we recommend upgrading to the latest JavaScript Agent. See Upgrade the JavaScript Agent. Upgrade the Mobile Agents See Upgrade iOS SDK for step-by-step instructions on upgrading manually or using CocoaPods. See Upgrade the Android Mobile Agent for step-by-step instructions on upgrading the Android SDK in your app. See Upgrade the Xamarin Agent for step-by-step instructions on upgrading the Xamarin Agent package in your app. Upgrade the IoT SDKs See Upgrade the IoT C++ SDK for step-by-step instructions. See Upgrade the IoT Java SDK for step-by-step instructions.   Additional Resources Instructions for upgrading other AppDynamics components are available in our general article,  How do I get started with upgrading my AppDynamics components? ... View more

Release Upgrade Checklist for Database Agents   NOTE : The information in this article is not release-specific. You can reference it for any release   To make sure you complete all the tasks necessary for upgrading Database Agents after a release, we recommend following the upgrade checklist instructions below.    Table of Contents Prepare to upgrade your Database Agents Plan your Database Agent upgrade Next Steps Troubleshooting Additional Resources   Prepare to upgrade your Database Agents Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your Database Agent upgrade Review the Agent/Controller compatibility matrix for compatibility mappings between agents and Controller versions. Supported Controller versions v.4.3 v4.4 v4.5 v20.3 - future releases DB Agent versions 4.1 - 4.3 (1) 4.1 - 4.4 (1) 4.1 - 4.5 (1) 4.1 - 20.x (1)(2)                (1) Controller version supports through the most recent release of the Database Agent                   (2) DB Agent is only compatible up to its corresponding Controller version      Before upgrading, we recommend completing two backups: Backup your previous installation of the Controller. Backup the <db_agent_home> directory so you can revert to the previous installation if required. To maintain the same configuration information, you will also need the <db_agent_home>\conf\controller-info.xml file. If you are upgrading both the Controller and agents, upgrade the Controller before upgrading the agents. See Upgrade the Database Agent for important upgrade notes and step-by-step instructions.    Next Steps For each database, you will need to configure the Database Collectors according to the database in your environment.  See Add Database Collectors in the documentation.   Troubleshooting If your database isn’t reporting, check Database Visibility System Requirements in the documentation If you are having problems with your Collector, see Add Database Collectors .  If your agents don’t seem to be reporting, see the Troubleshooting Collector Problems section under Add Database Collectors .   Additional Resources Instructions for upgrading other AppDynamics components are available in our general How do I get started with upgrading AppDynamics components for any release? ... View more

Release Upgrade Checklist for Machine Agents   Note: The information in this article is   not   release-specific. You can reference it for any release.   To make sure you complete all the tasks necessary for upgrading Machine Agents after a release, we recommend following the upgrade checklist instructions below.   Table of Contents Prepare to upgrade your Machine Agents Plan your Machine Agent upgrade Troubleshooting Additional Resources   Prepare to upgrade your Machine Agents Review the  Product Announcements and Alerts page  for details on any  intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? — especially the component compatibility matrix Technical Documentation: Agent and Controller Compatibility   Plan your Machine Agent upgrade   Review the Machine Agent and Controller version compatibility information below: Supported Controller Versions v4.3 v4.4 - 4.4.3 v4.5+ v20.3 - future release Machine Agent Versions 4.x - 4.3 4.4.1 - 20.x (1) 4.5 - 20.x (1) 4.4 - 20.x (1)(2) (1)   Controller version supports through the most recent released Agent version (2)  Controller does not support Agent version 4.1 Review the list of Machine Agent supported environments and versions to ensure compatibility between your Machine Agents and JDK. For example, 4.0.x is the latest version that can run on JDK 1.5 and higher, and any version from 4.1.x and higher needs JDK 1.7 or higher . See Upgrading the Machine Agent for step-by-step instructions. Note: It’s a good practice to back up the <machine_agent_home> directory to a <machine_agent_home_BACKUP>  in case you need to revert to the previous installation.   Troubleshooting In the event of an error condition, uninstall the new version and reinstall the previous version of the Machine Agent.   Additional Resources Instructions for upgrading other AppDynamics components are available in our general How do I get started with upgrading AppDynamics components for any release? ... View more

Release Upgrade Checklist for Java Agents   To make sure you complete all the tasks necessary for upgrading Java Agents after a release, we recommend following the upgrade checklist instructions below.    NOTE : The information in this article is not release-specific. You can reference it for any release   Table of Contents Prepare to upgrade your Java Agent  Plan your Java Agent upgrade  Shut down the JVM when uninstalling a Java Agent  Additional resources    Prepare to upgrade your Java Agent Review the Product Announcements and Alerts page for details on any intermediate versions between the current version of your instance and the version you are targeting. Review either of the following to confirm the compatibility of the various components of the AppDynamics environment: Knowledge Base article: How do I get started with upgrading my AppDynamics components for any release? , especially the component compatibility matrix Technical documentation: Agent and Controller Compatibility   Plan your Java Agent upgrade To ensure a successful correlation, upgrade agents on downstream tiers first, and then on upstream tiers. If you’re upgrading multiple agents in your monitored environment, upgrade the agents for the tiers on which business transactions are originated last. Starting in release 4.5, Java Agents are automatically backward-compatible with any 4.4.1+ Controller, so you can upgrade your agent while retaining your 4.4.1+ Controller. Note : If your Controller is older than 4.4.1, you must upgrade your Controller before upgrading your Java Agent. Supported Controller Versions v4.3 v4.4 v4.5 v20.3 - future releases Java 4.x - 4.3 4.4.1 - 20.x (1) 4.5 - 20.x (1) 4.4 - 20.x (1)(2) (1) Controller version supports through the most recent released Agent version (2) Controller version does not support Agent version 4.1   Review How does EUM component compatibility work? for compatibility mappings between agents and Controller versions See Upgrade the Java Agent for step-by-step instructions. See Install the AppDynamics Site Extension for Java for instructions for both minor and major releases.   Shut down the JVM when uninstalling Java Agents When uninstalling, it’s important to shut down the JVM that the Java Agent runs on, or the Java Agent will reappear in the UI. See Uninstall the Java Agent for the correct procedure.    Additional Resources Instructions for upgrading other AppDynamics components are available in our general release upgrade checklist,  How do I get started with upgrading AppDynamics components for any release? ... View more