Enable Exasol Admin in an existing deployment

Learn how to enable Exasol Admin in an existing Exasol deployment.

Introduction

You can enable Exasol Admin in the deployment configuration when deploying Exasol version 2025.1 or later. The service will then start automatically and the UI will be available once Exasol is up and running.

If you did not enable Exasol Admin in the configuration, or if you are updating from an earlier rolling release version of Exasol, you can enable Exasol Admin in an existing deployment.

This procedure uses Exasol Deployment Tool (c4).

Procedure

Step 1: Update Exasol to the latest version

We recommend that you update Exasol to the latest version following the instructions in Update procedure (command line).

If the parameter CCC_UPDATE_CCC is set to false in the configuration for your deployment, you will not be able to enable Exasol Admin after the update.

To set the parameter to true, use --ccc-update-ccc true with the c4 update cluster command.

Step 2: Set the admin password for Exasol Admin

  1. Connect to the node where you want to host Exasol Admin using c4 connect -i PLAY_ID -s host -n NODE_ID.

    Example:
    Copy 
    c4 connect -i c3275f84 -s host -n 11

  2. When connected to the node, find out the local play ID using c4 ps --local -e '.[].play.id'.

    Example:
    Copy 
    $ c4 ps --local -e '.[].play.id'
    cb58f289-ba1c-47e6-a632-7b85ac1ee921

  3. Set the password for the Exasol Admin user using the following command:

    Copy 
    c4 local reconf --ccc-adminui-admin-password-hash "$(c4 pwdhash -c -i <<< "<new_password>" | tr -d '\n'  | base64)" "<local_play_id>"
    Example:
    Copy 
    c4 local reconf --ccc-adminui-admin-password-hash "$(c4 pwdhash -c -i <<< "secretPassword123456" | tr -d '\n'  | base64)" "cb58f289-ba1c-47e6-a632-7b85ac1ee921"

Step 3: Enable the UI service

  1. To enable the exasol-admin-ui service, use the following command (while still connected to the node that will host Exasol Admin):

    sudo systemctl enable --now "exasol-admin-ui.service"

  2. Check that the service is running:

    sudo systemctl status exasol-admin-ui.service

Step 4: Add the EXA_PROUST_MONITOR user (if updating from 8.31.0 or earlier)

In order to generate database health charts and for the connection test function to work, Exasol Admin requires that the user EXA_PROUST_MONITOR exists in the database. If you are updating from Exasol version 8.31.0 or earlier, you must manually add this user if it does not exist.

If your deployment is a fresh installation of Exasol 8.32.0 or later, this step is not required.

  1. Connect to COS (if you are not already connected).

    Example:
    Copy 
    c4 connect -i c3275f84 -s host -n 11

  2. Run the following command to obtain the {plaintext_password} of the EXA_PROUST_MONITOR user that you will need in the next step:

    Copy 
    printf "%s\n" "$(grep ExaMonitorUserPassword /exa/etc/EXAConf | awk '{print $3}' | base64 -d)"

  3. Connect to the database and run the following statements:

    Copy 
    CREATE USER EXA_PROUST_MONITOR IDENTIFIED BY "{plaintext_password}";
    GRANT CREATE SESSION TO EXA_PROUST_MONITOR;
    GRANT SELECT ANY DICTIONARY TO EXA_PROUST_MONITOR;