Question
Bupa
AU
Last activity: 4 Jun 2024 21:24 EDT
Keeping both Files based as well as DB based IH in Pega 8.8
Hi,
We are currently on Pega 8.8.2 and are writing the interactions only to DB. We are now exploring the option of writing the results to files. My query is if I keep the writeToIH DSS as True and enable the export functionality as well by configuring the repository and folder settings and setting interactionHistory/writeToStream to true, will the summaries source their data from the files or the DB? My understanding is that it will still source from the DB but will also write the interactions to files.
If it sources the data from files, it will be very difficult to unit test the code because deleting entries from physical IH, deleting entries from ActionInsights2 and recreating aggregates is easier than managing that from files.
Also, is there a way to control the processing where the summaries are sourced only from DB but the interactions are also written to files for analysis?
Thanks, Chiranjeet
Pegasystems Inc.
GB
@ChiranjeetM17144809 If you set the writeToIH DSS to true and enable the export functionality, the system will save interactions both to the database and to the InteractionFiles data set. The InteractionFiles data set, also known as the replay data set, is read-only and configured as the destination for the data flow that exports interactions to the file repository. It is used to populate interaction history summaries with the latest interactions. However, during the transition period, the system keeps writing interactions to the pxInteractionHistory data set and the interaction history based on the relational database continues to work. This means that your interaction history summaries will still source their data from the database during this period. Once you fully migrate to the new interaction history architecture, the system will source the data from the files.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to migrate interactions
Migrating interaction history from the relational database to a file repository
@ChiranjeetM17144809 If you set the writeToIH DSS to true and enable the export functionality, the system will save interactions both to the database and to the InteractionFiles data set. The InteractionFiles data set, also known as the replay data set, is read-only and configured as the destination for the data flow that exports interactions to the file repository. It is used to populate interaction history summaries with the latest interactions. However, during the transition period, the system keeps writing interactions to the pxInteractionHistory data set and the interaction history based on the relational database continues to work. This means that your interaction history summaries will still source their data from the database during this period. Once you fully migrate to the new interaction history architecture, the system will source the data from the files.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Preparing to migrate interactions
Migrating interaction history from the relational database to a file repository
Recreating interaction history summaries
Bupa
AU
Thanks for your response. My query is what if we want to continue using the DB as the source for the summaries and use the files only for reporting and audit purposes? Let's say we maintain IH for 6 months so I understand that once we have files written for 6 months, DB will no longer act as the source for interactions. But how does Pega know when to switch to files even though writeToIH DSS is kept as true? And what if we want to continue using DB as the source?
Also, I suppose moving to files is difficult when it comes to unit testing because if we want to delete the entries for a particular customer and retest, it is difficult because we don't know which file Pega wrote that interaction to. So, is there a better way to perform unit testing once we move to file-based approach?
Thanks,
Chiranjeet