You can persist the EDA events that Task Engine emits to an event store of your choice using webMethods Event Persistence. You can use persisted task events for different purposes such as logging, archiving, and analytics. To emit events from Task Engine, you must configure EDA events as described in Administering Task EDA Event Emission.

Event Persistence can persist Task Engine events to different storage engines such as Elasticsearch and HDFS.

To store Task Engine events with Event Persistence, you must configure an Event Persistence service, as follows:

For information about how to create and configure Event Persistence services, see Software AG Command Central Help and Communicating Between Software AG Products Using Event Routing.

You can configure Task Engine to emit TaskChanged events for different task operations, such as creating, updating, and deleting a task instance. Event Persistence can store the TaskChanged events for all task operations. To enable or disable the emission of EDA events for a particular task operation, see About EDA Predefined Task Event Types.

You can control whether task business data is included in the EDA event, as described in About Global Settings for EDA Events. When persisted together with an event, task business data is encoded in Base64 format.