Try OpenEdge Now
skip to main content
BPM Events User's Guide
Administering and operating BPM Events : Persistence and recovery : Infopad persistence

Infopad persistence

Infopads are automatically persisted, and their database image is automatically synchronized with their memory image at the end of each external event processing. The persistent infopads are stored in the Business Process Server Infopad Repository in the database. This repository serves three purposes:
*Failure recovery.
*Real-time access from front-end user interfaces, by business users.
*Input of the infopad archiving utility.
When the in-memory processing of an external event EVT is completed successfully by the rule engine (remember that this may have involved possibly several rules, and possibly several internally generated events), then several infopads may have been modified as a result. These modifications are gathered and notified to the Business Process Server Infopad Repository though JDBC calls, as a single transaction, called the synchronization transaction. Only when this transaction succeeds, is the external event EVT considered as successfully processed. Only then is the next external event processed.