How does it manage sessions in Pega?

Question

NagaakiA16892568

Member since 2023

Kyndryl

Posted: Feb 28, 2024

Last activity: Mar 21, 2024

Posted: 28 Feb 2024 3:38 EST
Last activity: 21 Mar 2024 9:36 EDT

Closed

Solved

we use Pega as a single cluster on multi AZ in Openshift.

A database of Pega is active-standby with mirroring and, Pega accesses to a Virtual IP.

A user accesses to web(Pega) via load balancer.

in these environment,

1, How does a user manage a session?

2, How does Pega manage a session between databases?

3, if system failure with going down a container, what will be happened after changing active-standby of database?

***Edited by Moderator Rupashree S. to add Capability tags***

To see attachments, please log in.

Accepted Solution

Posted: 1 year ago

Updated: 1 year ago

Posted: 6 Mar 2024 8:38 EST
Updated: 21 Mar 2024 9:36 EDT

MarijeSchillern

MOD

replied to NagaakiA16892568

User sessions in Pega are managed through session-based affinity support. This ensures that requests from one user are directed to a specific application server that maintains the state for that user. It is a Pega best practice to use cookie-based session affinity.
Pega does not manage sessions between databases. Instead, it makes requests to a database. In a high availability setup, Pega supports database vendor-specific features and products for redundancy/failover at the database tier.
In the event of a system failure that results in a container going down, Pega's high availability features, combined with platform vendor solutions for database mirroring/DR and application server clustering, provide a comprehensive solution. If a node in the cluster crashes, Pega provides automated recovery support. The Pega platform is designed to store locally any in-process work, which allows the user to resume processing from the stopping point after a system interruption or failure.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

User sessions in Pega are managed through session-based affinity support. This ensures that requests from one user are directed to a specific application server that maintains the state for that user. It is a Pega best practice to use cookie-based session affinity.
Pega does not manage sessions between databases. Instead, it makes requests to a database. In a high availability setup, Pega supports database vendor-specific features and products for redundancy/failover at the database tier.
In the event of a system failure that results in a container going down, Pega's high availability features, combined with platform vendor solutions for database mirroring/DR and application server clustering, provide a comprehensive solution. If a node in the cluster crashes, Pega provides automated recovery support. The Pega platform is designed to store locally any in-process work, which allows the user to resume processing from the stopping point after a system interruption or failure.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Show Less

To see attachments, please log in.