Installation Guides › Policy Server Installation Guide › Installation Overview › SOA Security Manager Installation Roadmap

SOA Security Manager Installation Roadmap

Installing SOA Security Manager requires you to install and configure several components, all of which are shown in the following diagram of a basic sample installation:

You should install and configure the SOA Security Manager components in the order shown in the sample illustration, as follows:

1. Policy Server and FSS Administrative UI
   • The Policy Server provides policy management, authentication, authorization, and accounting services.
   • The FSS Administrative UI is installed with the Policy Server and is only used to manage CA SiteMinder Federation Security Services features. If you will not need to generate WS-Security SAML tokens, use of the FSS Administrative UI is not required. Although part of the core Policy Server installation, the FSS Administrative UI must be registered with the Policy Server before it may be used. Registering the FSS Administrative UI is completed through the Administrative UI. Therefore, you must install and configure the Administrative UI before registering the FSS Administrative UI.
2. Policy store ‑ The policy store contains all of the Policy Server data. You can configure a policy store in a supported LDAP or relational database.
3. Directory XML file—A directory xml file (directory.xml) describes how objects such as users, groups, and organizations are stored in your administrator user store. Prior to installing the Administrative UI, you configure a supported directory server or database-specific directory XML file so that the Administrative UI is able to locate your administrative users in the administrator user store.
4. Administrative UI—You use the Administrative UI to manage SOA Security Manager administrator accounts, objects, and policy data through the Policy Server. You configure a directory XML file, an administrator user store, and an object store when installing the Administrative UI:
   • Object store—The Administrative UI is an asynchronous application that is event and task-based. The object store stores information about these tasks and events. You configure an object store in either a MS SQL Server or Oracle database.
   • Administrator user store—The Administrative UI authenticates SOA Security Manager administrator accounts using the administrator user store. All of your administrator accounts must be stored in a single administrator user store. You configure an administrator user store in a supported LDAP directory server or ODBC database when installing the Administrative UI.

     Note: If you are upgrading to r12.1, you may use an existing user store as an administrator store.

   Note: CA recommends installing the Administrative UI on a system that is not hosting the Policy Server.

5. SOA Agent (or SOA Security Gateway)—A SOA Agent is integrated with a web server or application server. The Agent lets SOA Security Manager manage access to web services according to predefined security policies. A SOA Agent is also integrated into the SOA Security Gateway, which provides XML gateway functionality in addtion to SOA Security Manager access control.

   Note: CA recommends installing SOA Agents and SOA Security Gateways on systems that are not hosting the Policy Server.

SOASM--SOA Agent Doc Reference Note

Note: More information on installing a SOA Agent exists in the SOA Security Manager Implementation Guide.