The purpose of the following use cases is to get you thinking about your SiteMinder architecture in terms of high availability and performance. The use cases begin with a simple deployment and progress into more complex scenarios. Each case is based on the idea of a logical "block" of SiteMinder components and illustrates how an environment can contain multiple blocks to address the following architectural considerations:
Extrapolate the necessary infrastructure from these cases to:
The simplest SiteMinder deployment requires one "block" of components. A block of components is a logical combination of dependent components that include:
You protect web-based resources by deploying at least one block.
The following diagram illustrates a simple deployment:
Each component has a specific role with resource protection.
Note: For more information about the primary purpose of each component, see SiteMinder Components.
|
Copyright © 2012 CA.
All rights reserved.
|
|