Pega Platform servers must be designed to support redundancy among Pega Platform various components, such as connectors, services, listeners, and search. The exact configuration varies based on the specifics of the applications in the production environment.

For more information, see Configuring SSO login authentication with a SAML identity provider.

To use filesystem passivation for high availability, you must select a fault-tolerant shared storage solution and integrate it with Pega Platform. Application servers require fault-tolerant shared storage in order to facilitate initiated and uninitiated shutdowns. Pega Platform supports shared storage using Network File Storage (NFS) or shared disk out of the box when using filesystem passivation, but these solutions are not inherently fault tolerant.

• For NFS solutions, the shared storage must point to an NFS location to support access from all nodes.
• For disk-oriented solutions, Pega Platform servers require read/write access to shared storage.

To support crash recovery when your system uses file system storage, the setting storage/class/passivation:/rootpath must be set to shared storage that is available to all servers in the cluster. For example: <env name="storage/class/passivation:/rootpath" value="P:\passivation" />.

• Depending on the operating system, the details of the configuration will vary.
• Shared storage should be deployed so it is not a single point of failure.
• Shared storage itself should have a failover solution.
• Server restart is required to change the location of shared storage in the Pega Platform.

For more information, see Configuring your system for passivation and activation.