Installation Guides › Implementation Guide › Architectural Considerations › Architectural Use Cases › Redundancy and High Availability › Agent to Policy Server Communication › Failover

Failover

Failover is the default HCO setting. In failover mode, a SOA Security Manager Agent delivers all requests to the first Policy Server that the HCO lists and proceeds as follows:

1. If the first Policy Server does not respond, the Agent deems it unavailable and redirects the request, and all subsequent requests, to the next Policy Server that the HCO lists.
2. If the first two Policy Servers do not respond, the Agent deems both of them unavailable and redirects the request, and all subsequent requests, to the next Policy Server that the HCO lists.

Note: For more information about configuring an HCO with multiple Policy Servers, see the [set the co variable for your book].

If an unresponsive Policy Server recovers, which the Agent determines through periodic polling, the Policy Server is automatically returned to its original place in the HCO list and begins receiving all Agent requests.

The following diagram illustrates the Agent failover process:

More information:

Multiple Components for Operational Continuity

Clustered Components for Scale