Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

    No Format
    bin/ 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\ file in the new Events Service directory. Depending on which type of deployment you are using, this involves inspecting and migrating settings from:
    •, or

    If you are upgrading from 4.2 to 4.3.x or a later version you must edit the file by replacing the port ranges [9300-9400] with :9300.

    For example, in 4.2, the file looks like this:

    No Format[9300-9400],[9300-9400],[9300-9400]

    While in 4.3 or later, the file should look like this:

    No Format,,
  6. Move property  property in while upgrading from 4.2 to 4.3.x or later.

  7. Verify that the new Events Service home directory exists. The Event Service home directory is determined by the property  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
  8. Move (do not copy) the old Events Service data directory to the new Events Service home directory directory. For example: 

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

    No Format
    nohup bin/ start -p conf/ &
  10. Check the health API of the node.
    For information on performing these steps, see Install the Events Service on Windows.