Implementation Guide › Architectural Considerations › Architectural Use Cases › Simple Deployment with Optional Components

Simple Deployment with Optional Components

You can extend the functionality of a simple deployment through the use of optional SiteMinder components. The decision to implement optional components is determined by the SiteMinder features your enterprise requires. For example:

• If you are planning to implement Federation Security Services, your environment requires a smkeydatabase and a session store.
• If you are planning to create audit-based reports, your environment will require a Report Server and an audit database.

The following diagram illustrates the optional components and their required dependencies:

• A Report Server
• A report database
• An audit database
• A key store
• A session store
• An smkeydatabase

  

Each component has a specific role in resource protection.

Note: For more information about the primary purpose of each component, see SiteMinder Components.

More information:

SiteMinder Components

Simple Deployment with Optional Agents

You can extend the functionality of a simple deployment your environment to protect resources that do not reside on a Web Server. For example, if your environment hosts resources on an:

• Application server, you can implement Application Server Agents to protect them.
• ERP system, you can implement ERP Agents to protect them.

The following diagram illustrates optional Agents:

Each component has a specific role with resource protection.

Note: For more information about primary purpose of each component, see SiteMinder Components.

More information:

SiteMinder Components