Defining passivation storage
Pega Platform provides two passivation storage mechanisms: database and filesystem. The default passivation storage is database, which is most efficient and robust.
You can override the default storage mechanism by setting the prconfig dynamic system settinginitialization/persistrequestor/storage to either
database, filesystem, or custom. Database passivation storage corresponds to the following prconfig.xml file setting:
<env name="initialization/persistrequestor/storage" value="database" />With database storage, the passivation daemon saves requestor information as an instance of
the System-Requestor-Context class, corresponding to the
pr_sys_context database table. The daemon saves page details as an
instance of the System-SavedPages class in the
pr_page_store database table.
To save passivation details in filesystem storage instead of the database, add following setting to the prconfig.xml file. For more information on filesystem storage, see Shared filesystem storage.
<env name="initialization/persistrequestor/storage value="filesystem" />- Implementing a custom passivation storage mechanism
Pega Platform provides two passivation storage mechanisms: database and filesystem. To use a custom passivation mechanism, you write a java class and update two prconfig settings.
Previous topic Changing the default passivation time-out settings Next topic Implementing a custom passivation storage mechanism