Skip to main content

 –

Defining passivation storage

Suggest edit Updated on August 18, 2021

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 setting initialization/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" />
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us