AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    1 Star2 Star3 Star4 Star5 Star
    32 rates

    To upgrade the Enterprise Console, you run the installer for the version of the application to which you want to upgrade on the Enterprise Console machine. The installer detects the Enterprise Console installation and upgrades that instance.

    About the Upgrade

    • You can upgrade across multiple versions at a time; that is, you do not need to run the installer individually for each intermediate version.
    • If you upgrade the Enterprise Console to 4.5.x version, it will copy the Controller and Events Service artifacts into the platform-admin/archives/<service>/<version> folder. When you upgrade to the next version of the Enterprise Console, the same will be repeated for newer binary versions, e.g. 4.5.1, 4.5.2, 4.6. Note that it is not possible to downgrade the Enterprise Console to any intermediate version.

      If you are upgrading from Platform Admin 4.3.x to the Enterprise Console, make sure you specify a different installation path from the Platform Admin 4.3.x. This is will ensure that any existing Events Service managed by the Platform Admin 4.3.x can be discovered and upgraded using the Enterprise Console.
    • You can enable HTTPS for the Enterprise Console during upgrades. See HTTPS Support for the Enterprise Console for more information.

    Before Upgrading

    • Before you start upgrading the Enterprise Console and your platform, make sure that you are using the correct upgrade order.
    • The user upgrading the Enterprise Console should be the same user who installed the Enterprise Console.

    • Make sure your Enterprise Console is running before you run the upgrade. This is to validate the Database Root User Password and Platform Admin Database Password. You will need to input the passwords when upgrading through the GUI.
    • For first-time upgrades, you need to use the same response file you used for your silent install. See Silent Installation.
    • Irrespective of first time or subsequent upgrades, you need to provide the relevant passwords in the response file.

    Upgrade the Enterprise Console

    The following steps describe how to upgrade the Enterprise Console on Linux and Windows. You use the Enterprise Console installer in GUI mode, console mode, or silent mode to perform the upgrade.

    GUI Installation

    If there is a newer version of Enterprise Console available, you can begin the upgrade process by downloading and installing the latest version from the AppDynamics download site on top of the existing application.

    Before starting, get the Enterprise Console installer version appropriate for your target system. You can get the installer from the AppDynamics download site. When ready, follow these steps to install the Enterprise Console: 

    1. Navigate to the directory where you downloaded the install file.
    2. Run the following commands:


      You can run the installer as non-root or root. 



      It is recommended that you right-click the exe and select Run as Administrator.

    3. After the GUI launches, use it to complete the installation. In Linux, you may also follow the steps in the installation wizard to complete the console installation.

      If you install the Enterprise Console on AWS, use the public DNS for the Enterprise Console host name when prompted.

    Silent Installation

    To use silent mode, pass the response file that the installer generated at first installation to the installer. This response file is at the following location

    •  <Enterprise_Console_home_directory>/.install4j/response.varfile

    If you have made any changes to the settings as originally configured by the installer—such as to the connection port numbers, tenancy mode, or data directory—make the same change in the response file before starting the upgrade. 

    You must also add the existing passwords to the file:

    platformAdmin.databasePassword= ENTER_PASSWORD
    platformAdmin.databaseRootPassword= ENTER_PASSWORD
    platformAdmin.adminPassword= ENTER_PASSWORD

    If you do not, the installer prompts you to add the password.  

    After Upgrading

    If you are upgrading the Enterprise Console from a version earlier than 4.5.9, you must clear your browser cache after the upgrade process completes.

    • No labels