Implementation Guide › Architectural Considerations › Architectural Use Cases › Multiple Components for Operational Continuity

Multiple Components for Operational Continuity

You can implement multiple blocks of components to build redundancy and failover into the environment. This use case builds on a simple deployment to explain how you can begin thinking about operational continuity. The following diagram illustrates:

• Multiple Agent instances intercepting user requests. As illustrated, each Agent is configured to initialize and communicate with a primary Policy Server and failover to the second Policy Server.
• A Policy Server cluster evaluating and enforcing access control policies. Load is dynamically distributed between each Policy Server in the cluster.
• Multiple user store connections. Each Policy Server is configured to communicate with a primary user store. The primary user store connection is configured with a secondary user store connection. The Policy Servers load balance requests for user information across both connections. If the primary connection becomes unavailable, Policy Servers failover to the secondary connection.
• A single policy store instance. Each Policy Server connects to the same policy store for a common view of policy information. The primary policy store connection is configured with a secondary connection to which the Policy Servers can failover.

  `

Each component has a specific role with resource protection.

Note: For more information about the primary purpose of each component, see SiteMinder Components. For more information about SiteMinder redundancy and high availability, see Redundancy and High Availability.

More information:

SiteMinder Components

Redundancy and High Availability