External Data Mart persistence

Last Updated : Feb 23, 2023 |

There are two types of persistence modes that you can use for External Data Mart: Audit and Journey.

Audit mode

In Audit mode, a new copy of the context is written to the database every time you modify a context.Consequently, a detailed audit trail of changes made to the context is created. This database can become large and consume a lot of disk space, impacting system performance.

You can use excerpts from this audit trail for context resurrection and customer journey.

Journey mode

In Journey mode, only a smaller subset of data is written each time you modify the context, representing a journey of the context through the system. Additonally, a single entry is persisted and updated for each context ID.

Although more efficient, Journey mode can only be used for context resurrection and customer journey. It does not maintain a full audit log.

When you use Context Store with Avaya Oceana®, the system supports only the Journey persistence type.

Note:

Data is not shared between these two persistence types. If you change the persistence type after the system is in use, all the data saved in the EDM using the previous persistence type becomes inaccessible.