Camunda Engine Data Reimport
There are cases where you might want to remove all Camunda BPM engine data from Optimize which has been imported from connected Camunda engines but don’t want to lose Optimize entities such as collections, reports or dashboards you created.
Please be aware that triggering a reimport causes the current data imported from the engine to be deleted and a new import cycle to be started. That also means that data which has already been removed from the engine (e.g. using the history cleanup feature) is irreversibly lost.
Please note that when triggering a reimport, all existing Event Based Processes get unpublished and reset to the
mapped state. This is due to the fact that Event Based Processes may include Camunda Engine data, yet the reimport does not take into account which sources Event Based Processes are actually based on and as such clears the data for all of them.
You then have to manually publish Event Based Processes after you have restarted Optimize.
To reimport engine data, please perform the following steps:
- Stop Optimize, but keep Elasticsearch running (hint: to only start Elasticsearch without Optimize, you can use
From the Optimize Installation root run
./reimport/reimport.shon Linux or
reimport/reimport.baton Windows and wait for it to finish
- in docker environments you can simply override the command the container executes on start to call the reimport script, e.g. in docker-compose this could look like the following:
version: '2.4' services: optimize: image: registry.camunda.cloud/optimize-ee/optimize:latest command: ["./reimport/reimport.sh"]
Start Optimize again. Optimize will now import all the engine data from scratch.
If you made use of Event Based Processes you will have to manually publish them again.