Skip to end of metadata
Go to start of metadata

On this page:

This page describes how to upgrade an EUM Server to version 4.4 of the latest production installation. This is usually done alongside an upgrade to the other platform components, such as the Controller and Events Service. 

Who Should Use This Document

Anyone wanting to upgrade the EUM Server to the latest available version should use this document.

For those users who are currently running a production EUM Server 4.3 or earlier, you will also have to run step 6 to import the data from your current production EUM Server to the latest 4.4 production EUM Server.

Before You Begin

Before you start upgrading the EUM Server, make sure that you are using the correct update order.

Upgrade Procedure

In addition to showing you how to upgrade your EUM Server, the instructions below also show you how to migrate the EUM data because, for the 4.4 production EUM Server, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine.

To upgrade the EUM Server to the latest production installation:

  1. Stop the EUM Server.
  2. Back up the old EUM data:
    1. On the Server host, back up the old version by copying the <eum_server_home> (i.e., <installDir>/AppDynamics/EUM) directory to a safe location.
    2. From a terminal, change to <controller_home>/db/bin and dump the database eum_db to a file:

      ./mysqldump -u root --password --protocol=TCP -P [Controller-MySQL-Port] --databases eum_db --add-drop-database > eum_db.sql
  3. Run the 4.4 EUM Server installer on the EUM host machine and follow the steps as prompted. For detailed instructions, see Install a Production EUM Server.

  4. 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
  5. Stop new install of the EUM Server.

  6. This step is only for those upgrading from a production EUM Server 4.3 or earlier. 
    ollow the instructions below to import the old EUM data to your new 4.4 production EUM Server. 
    1. Copy the old EUM data (see step 2a) to the directory <eum_server_home>/store on the host of the 4.4 EUM Server.

    2. Edit the file <eum_server_home>/eum-processor/bin/liquidbase.properties, and set a password for the password property.
    3. Change to <eum_server_home>/mysql/bin.
    4. Drop all the tables in the eum_db database in the new EUM MySQL instance:
      1. List the tables you need to drop:

        ./mysql -u eum_user --password eum_db --protocol=TCP -P [EUM-MySQL-Port] -e "show tables"
      2. From the displayed list of tables, run the following command for each table to drop. Be sure to replace [tableName] with the name of the table to drop.

        ./mysql -u eum_user --password eum_db --protocol=TCP -P [EUM-MySQL-Port] -e "drop table [tableName]"
    5. Import the backed-up MySQL tables to the new database:

      ./mysql -u root --password --protocol=TCP -P [EUM-MySQL-Port] < <controller_home>/db/bin/eum_db.sql
    6. If you are upgrading from (, 4.0.8, 4.0.9, 4.0.10, 4.1.x), run:

      ./mysql -u root -p eum_db --protocol=TCP -P [EUM-MySQL-Por] < <eum_server_home>/eum-processor/bin/407to410.sql
    7. Upgrade schema to version 4.4:

      cd <eum_server_home>/eum-processor/bin/
      bash ./eum-schema update
    8. After the database is set up, remove or replace the password for the property in the file <eum_server_home>/eum-processor/bin/liquibase.properties.

  7. If your older version of the EUM Server was not using an HTTPS proxy, but was using HTTPS, edit the file <eum_server_home>/eum-processor/bin/eum.properties, set the property processorServer.httpsProduction to true, and assign your HTTPS port to the property processorServer.httpsPort.


  • No labels