Generally, you can just upload the latest service repository to update the Process Mining services. Just take note of the following:

If not only the last but the second number of the version has changed, there could have been an API update. In this case, check if the service settings have changed. In case the service settings have changed, the best is to start with a clean DB and re-import the logs of the last x days you need.

If this is not feasible, analytics-etl-service will update the DB on startup. We recommend saving a database backup before updating the database, in case of problems during the update.

However, with updating analytics-etl-service there are some restrictions and you have to follow the procedure described below.

Updating analytics-etl-service

To update the analytics-etl-service safely, proceed as follows:

  1. Stop the analytics-collector-service.
  2. Wait, until analytics-etl-service has processed all log files from the queues.
  3. Stop analytics-etl-service.
  4. Upload the new repository of analytics-etl-service.

  5. If not only the last but the second number of the version has changed, there could have been an API change:

    • Check, if the service settings have changed.
    • Update analytics-collector-service as well.
  6. Start analytics-etl-service.
  7. Start the analytics-collector-service.

Updating the Database

You will not have to update the database manually. If the ETL service needs a newer database version, it will upgrade the database automatically on start-up.

On this Page:

  • No labels