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, TrxLogsETL 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 TrxLogsETL there are some restrictions and you have to follow the procedure described below.

Updating TrxLogsETL

You cannot update major versions automatically. If the first number of the version has changed, the database won't be automatically updated.

To update the TrxLogsETL safely, proceed as follows:

  1. Stop all log collector services TrxLogCollector on all BRIDGES.
  2. Wait, until TrxLogsETL has processed all log files from the queues.
  3. Stop TrxLogsETL.
  4. Upload the new repository of TrxLogsETL.

  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 TrxLogsCollector as well.
  6. Start TrxLogsETL.
  7. Start all log collector services TrxLogCollector on all BRIDGES.

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.