Passivation and activation

Passivation and activation help with system performance and failover.

Passivation

Passivation removes operator data from memory if an operator is not active.

If high availability is enabled, the Pega Platform uses database passivation by default, with filesystem passivation available as an alternate method. If high availability is not enabled, the Pega Platform uses either the configured location (filesystem or database), or, if no location is configured, the temp folder.

Note: The default passivation directory is the operating-specific temporary directory and cannot be used for passivation storage.

To add a process to occur before passivation (for example, saving all call data and closing all tabs in a customer service application), use the pyPrePassivation activity. In order for this activity to be run as expected, you must implement the activity with the correct applies-to class (@baseclass).

Note: The pyPreQuiescePassivation activity is deprecated.

Activation

If the operator continues working after a period of inactivity, the system retrieves their work from storage and puts it back into memory, referred to as activation.

To add a process to occur after activation (for example, reconnecting a user with a dropped call), use the pyPostActivation activity. In order for this activity to be run as expected, you must implement the activity with the correct applies-to class (@baseclass).

Note: The pyPostQuiesceActivation activity is deprecated.