Installation Guides › Policy Server Installation Guide › Configuring LDAP Directory Servers as a Policy or Key Store › Installation Road Map

Installation Road Map

The following diagram illustrates a sample SOA Security Manager installation and lists the order in which you install and configure each component.

• The components surrounded by a solid line represent the Policy Server and a non-registered FSS Administrative UI. A Policy Server must be installed before configuring a policy store. Do not continue with the installation process if a Policy Server is not yet part of your environment.

  Note: The FSS Administrative UI is installed with the Policy Server. Unless you need to generate WS-Security SAML assertion tokens, you may safely leave the CA SiteMinder Federation Security Services on the Policy Server machine without registering it with the Policy Server.

• The component surrounded by a green dotted line represents the policy store, which you configure at this point in the installation process. The policy store contains all of the Policy Server data. You configure a policy store in either an LDAP or relational database.

  Note: The following figure depicts a single policy/key store instance. Although not illustrated, your environment may use separate instances for individual policy and key stores.

  

The following sections in the documentation detail how to:

• Configure the policy store.
• Establish a connection to the Policy Server.

Note: If you are trying to configure or upgrade a SOA Security Manager store listed in the SOA Security Manager Platform Support Matrix and cannot find the procedures in this guide, see the Directory Configuration Guide.