This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.

On this page:

Your Rating:
40 rates
This topic describes how to upgrade a manually installed standalone Events Service. The Events Service instance that is embedded with the Controller is upgraded automatically when you upgrade the Controller using the installer. For non-embedded (that is, remote) Events Service nodes, you need to follow the steps here to upgrade the Events Service software to 4.2. 

If you manage the Events Service using the Platform Administration Application, see Install the Events Service on Linux for upgrade instructions. 

About the Upgrade

This page describes how to upgrade a manually installed Events Service instance. 

The procedure requires the Event Service process to be briefly shut down. If you have deployed the Events Service in a cluster, you can perform the upgrade procedure as a rolling upgrade, avoiding service downtime. As a rolling upgrade, you upgrade each machine while the other cluster nodes continue to respond to client requests.

For an Events Service deployment you have installed and manage with the Platform Administration Application, you can use the Platform Administration Application. To use the application to upgrade the Events Service, you must upgrade the Controller, which also upgrades the Platform Administration Application version.  

Perform the upgrade in the following order if you did not use the Platform Administration Application to install the Events Service:

  1. Upgrade the Events Service
  2. Upgrade the EUM Server
  3. Upgrade the Controller

Perform the upgrade in the following order if you used the Platform Administration Application to install the Events Service:

  1. Shutdown the EUM Server
  2. Upgrade the Controller
  3. Upgrade the Events Service with the application.
  4. Upgrade the EUM Server.

Note that upgrading platforms that use the Platform Administration Application results in downtime of the EUM Server.

Upgrade the Events Service

  1. Download the Events Service distribution, events-service.zip, from the AppDynamics download site to the Events Service machine. 
  2. Stop the Events Service processes: 

    bin/events-service.sh stop
  3. Rename the existing Events Service directory, for example, to events-service-backup. 
  4. Unzip the Events Service distribution archive you downloaded to the location where you want the Events Service to run. 
  5. Migrate configuration changes from the properties files in the backup Events Service directory to the conf\events-store-api-store.properties file in the new Events Service directory. Depending on which type of deployment you are using, this involves inspecting and migrating settings from:
    • events-service-all.properties, or
    • events-service-api-store.properties
  6. Verify that the new Events Service home directory exists.  The Event Service home directory is determined by the ad.es.path.home property in the property file used to start up the Events Service. 
    If the directory does not exist, create it.  For example, create the following directory:  /opt/appdynamics/events-service/appdynamics-events-service
  7. Move (do not copy) the old Events Service data directory to the new Events Service home directory directory. For example: 

    mv /opt/appdynamics/events-service-backup/appdynamics-events-service/data /opt/appdynamics/events-service/appdynamics-events-service/
  8. Restart the Events Service processes from the new directory:

    nohup bin/events-service.sh start -p conf/events-service-api-store.properties &
  9. Check the health API of the node.

    For information on performing these steps, see Install the Events Service on Windows.



  • No labels