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

Prerequisite

Java 1.8 is required for events-service.exe to work.

To upgrade the Events Service manually:

  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. Configure the connection to the Events Service in the Controller, and get the Controller key for the Events Service configuration as follows:

    1. With the Controller running, open the Administration Console as the root user. 
    2. In the Controller Settings page, search for appdynamics.on.premise.event.service.url.
    3. Replace the default value to the internal hostname for the Events Service machine and default Events Service listen port, 9080.
    4. Search for an additional setting, the one you will need to enable the connection from the Events Service to the Controller, appdynamics.on.premise.event.service.key. 

    5. Copy the value of the property to your clipboard. You will need to configure this in the Events Service properties file next. 

  7. Configure the connection from the Events Service to the Controller:

    1. In a terminal, navigate to the  events-service directory:

      cd events-service

    2. Open the conf\events-service-api-store.properties file for editing

    3. Find the following property and replace controller-key with the copied key: 

      ad.accountmanager.key.controller=controller-key

  8. Ensure that the following critical properties are configured appropriately in the events-service-api-store.properties file:

    • ad.accountmanager.keyNamesCSV=EUM,CONTROLLER,MDS,OPS,SLM,JF
    • ad.accountmanager.key.eum=
    • ad.accountmanager.key.controller=
    • ad.accountmanager.key.mds=
    • ad.accountmanager.key.ops=
    • ad.accountmanager.key.slm=
    • ad.accountmanager.key.jf=
    • ad.accountmanager.key.service=
    • ad.jvm.heap.min=1g
    • ad.jvm.heap.max=1g
    • ad.es.jvm.heap.min=1g
    • ad.es.jvm.heap.max=1g

  9. Move ad.es.node.unicast.hosts property in events-services-api-store.properties while upgrading from 4.2 to 4.3.x or later.

  10. Save and close the events-service-api-store.properties file. 
  11. 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

  12. 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/

  13. Restart the Events Service processes from the new directory:

    nohup bin/events-service.sh start -p conf/events-service-api-store.properties &
  14. Check the health of the node.
    Windows
    bin\events-service.exe check-health -hp localhost:9081
    Linux
    curl -XGET localhost:9081/healthcheck?pretty=true

    Verify that "Healthy" appears as the service status, indicating that the process is operating normally:
    [appduser@controller-one events-service]$ bin/events-service.exe check-health -hp 192.168.33.22:9081
[2015-12-09T18:30:45,342-08:00] HV000001: Hibernate Validator 5.0.2.Final
[2015-12-09T18:30:45,956-08:00] Individual statuses below:
[2015-12-09T18:30:45,956-08:00] [192.168.33.22:9081] status is [200 OK]
[2015-12-09T18:30:45,956-08:00] Overall status Healthy
    ...

  15. Configure the connections from the Analytics Agent, EUM Server, or Database Monitoring agents to the Events Service, as described in Connect to the Events Service.
    For information on performing these steps, see Install the Events Service on Windows.

If you upgrade to 4.4.x 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.