Installation Guides › 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 SOA Security Manager components. The decision to implement optional components is determined by the SOA Security Manager features your enterprise requires. For example:

• If your web service implementations will require SOA Security Manager to sign and validate signed messages with WS‑Security tokens, or to produce or consume XML encrypted messages with WS‑Security tokens, your environment requires an smkeydatabase.
• 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 SOA Security Manager Components.

More information:

SOA Security Manager Architecture and Components