On this page:


Your Rating:
Results:
PatheticBadOKGoodOutstanding!
13 rates
This topic describes how to manually upgrade an Events Service. This is useful for when you did not use the Platform Administration Application or the Enterprise Console to deploy the Events Service. The primary case for this would be for when you need to upgrade the Events Service nodes hosted on remote Windows machines.

Perform the Manual Upgrade

Perform the following tasks to upgrade the Events Service manually. Note that Java 1.8 is required for events-service.exe to work.

  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

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

    For example, in 4.2, the events-service-api-store.properties file looks like this:

    ad.es.node.unicast.hosts=node1.example.com[9300-9400],node2.example.com[9300-9400],node3.example.com[9300-9400]

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

    ad.es.node.unicast.hosts=node1.example.com:9300,node2.example.com:9300,node3.example.com:9300
  6. Move ad.es.node.unicast.hosts property in events-services-api-store.properties 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 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
  8. Move (do not copy) the old Events Service data directory to the new Events Service home directory. For example: 

    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:

    nohup bin/events-service.sh start -p conf/events-service-api-store.properties &
  10. Check the health API of the node.
    For information on performing these steps, see Install the Events Service on Windows.

If you upgrade to 4.4.x or later from 4.3.x or an earlier version, the commands to start and stop the Events Service change. See Administer the Events Service for more information.

 

 

  • No labels