PDFs


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


Skip to end of metadata
Go to start of metadata

On this page:


This page describes how to upgrade an EUM Server to the latest version. Normally, this would be done alongside an upgrade to the other platform components, the Controller and Events Service. 

Upgrade the EUM Server

To upgrade the EUM Server, follow these steps:

  1. Stop the EUM Server.
  2. On the Server host, back up the old version by copying the <eum_server_home> directory to a safe location.
  3. Run the new installer on the Controller host machine and select option 2. 
  4. Run the new installer on the EUM host machine and select option 3.
  5. (Optional) After the installation has completed, if you are using HTTPS:
    1.  Edit the $APPDYNAMICS_HOME/EUM/eum-processor/bin/eum.properties with a text editor.
    2. Add the following properties to the eum.properties file:
      • processorServer.keyStorePassword=
      • processorServer.keyStoreFileName=
    3. Assign new values to these properties or copy and paste the values from the eum.properties file from your 4.2 EUM Server.
    4. Restart the EUM Server.
  6. Confirm that the EUM Server is running by making a cURL request to your EUM Server. The server will respond with ping as shown below.
    $ curl http(s)://<eum_server_host>:<port>/eumcollector/ping
    ping

Verify EUM Server Configuration after a Controller Upgrade

In version 4.2 of the AppDynamics Application Intelligence Platform, configuration settings previously in the domain.xml file in the Controller application server configuration have been moved to be Controller Settings, which are accessible in the Controller Administration Console.

The Controller upgrade process takes care of the settings migration for you, but you may wish to verify the upgrade configuration as described here.  

To verify EUM settings in the Controller configuration:
  1. From a terminal, navigate to the following directory on the Controller machine:  
    <controller_home>/appserver/glassfish/domains/domain1/config 
  2. Open the backup of the domain.xml file generated during the upgrade process. The backup file is located in the same directory and is named with the following pattern, where yyyyMMdd_HHmmss is the time at which the backup was created: 

    domain.xml_yyyyMMdd_HHmmss.bak
  3. Compare the JVM options indicated below from the backup domain file to the equivalent Controller Settings in the Administration Console: 

    JVM Options from domain.xml.bakEquivalent Global Controller Setting
    appdynamics.controller.eum.cloud.hostNameeum.cloud.host
    appdynamics.controller.eum.beacon.hostNameeum.beacon.host
    appdynamics.controller.eum.beacon.https.hostNameeum.beacon.https.host
    appdynamics.controller.eum.analytics.service.hostNameeum.es.host

    In the file, the JVM options appear as -D system property arguments within jvm-options tags. For example:

    <jvm-options>-Dappdynamics.controller.eum.cloud.hostName=http://controller.example.com:7001</jvm-options>
  4. If you notice any discrepancies, ensure that the Controller Setting has the correct value. 

  • No labels