HTTP session passivation mechanism

General
1

Question#1 (HTTP session passivation)

How to enable HTTP session passivation? If I enabled HTTP session passivation, does other types of passivation also kick in? (page passivation, timeout passivation). I understand that HTTP passivation is mandatory for the High availability (in case of node crash). So, is it enabled by default?

In https://community.pega.com/sites/pdn.pega.com/files/help_v81/procomhelpmain.htm#engine/passivation/eng-http-session-passivation-ref.htm, It was mentioned that the DSS/prconfig Initialization/PersistRequestor to be OnTimeout.

In Understanding passivation and requestor timeouts , it was mentioned that the Initialization/PersistRequestor to be AtInteractionEnd

Question#2

In https://community.pega.com/sites/pdn.pega.com/files/help_v81/procomhelpmain.htm#engine/passivation/eng-timeout-passivation-ref.htm, it was mentioned that the Timeout passivation is for single-node system. Is that correct?

Question#3

https://community.pega.com/sites/pdn.pega.com/files/help_v81/procomhelpmain.htm#engine/passivation/eng-page-passivation-ref.htm

Out of the 3 possible passivation types (Page, Timeout and HTTP session), what is the default passivation mechanism? Does Page passivation enabled by default? Does Page passivation passivates requestors also? If yes, how is it different from the Timeout passivation?

2

Yes - that’s correct on Question2

Yes, it is correct that timeout passivation is often described in the context of single-node systems. In a single-node setup, its primary purpose is to allow a user to resume work without losing context after their session has timed out due to inactivity. In a multi-node environment, this same mechanism is extended to support failover (HTTP session passivation), allowing the session to be reactivated on a different node if the original node fails.