Replaying Case events

If you need to regenerate your business data in specific scenarios, you can replay Case events by stopping the event emitter, clearing data, stopping the Flink job, and finally restarting the emitter.

Before you begin

It is assumed that the following prerequisites are met:
  1. You have configured HDFS and Elasticsearch, and you know what folders are configured.
  2. The necessary permissions are granted to the user with administrator role who runs the commands.
  3. You have configured the required tools , including cloudctl, kubernetes, jq, to work with the IBM® Cloud Private environment.
  4. From the date of the configuration on, the events in Content Platform Engine are not pruned before the replay procedure, because after the replay procedure, the Case event emitter starts pushing the events that exist in the Content Engine database, based on the configured date.

About this task

Replaying Case events consists in reprocessing the emitted Case-related events to regenerate the data for Case dashboards and data science applications. This process applies only to Case data. It is helpful to support troubleshooting and usage scenarios such as the following ones.
  • The target object store is reset.
  • The Case event emitter needs to be reconfigured to include events of a different solution.
  • New fields that were included in subsequent releases of IBM Business Automation Insights need to be backported for older data.
Attention: Be very careful when you type in the folder and index names because, if incorrectly used, the same commands can delete BPMN data.

Make sure to complete all the following steps.

Parent topic: Troubleshooting the Case event emitter