Installation Guides › Policy Server Installation Guide › Installing the Policy Server on UNIX Systems › How to Install the Policy Server › Policy Server Component Considerations

Policy Server Component Considerations

The Policy Server installer can configure the following components. Consider the following before running the Policy Server installer:

• FSS Administrative UI—The FSS Administrative UI is installed with the Policy Server and is for managing CA SiteMinder Federation Security Services. If your organization is not federating with a partner, use of the FSS Administrative UI is not required. Although part of the core Policy Server installation, the CA SiteMinder Federation Security Services must be registered with the Policy Server before it can be used. Registering the FSS Administrative UI requires the use of the Administrative UI. Therefore, install and configure the Administrative UI before registering the FSS Administrative UI.
• Web Server—A supported web server is required to configure the FSS Administrative UI. The Policy Server installer configures the FSS Administrative UI with the selected web server.
• OneView Monitor—The OneView Monitor enables the monitoring of SiteMinder components.

  Note: To use the OneView Monitor, you must have the supported Java SDK and ServletExec ISAPI Windows/IIS installed.

• SNMP—You must have the password of the root user and have a native SunSolstice Master Agent to enable SNMP support.
• Policy Store—The policy store is the repository for Policy Server objects and policy information.
• SOA Security Manager Key Database (smkeydatabase)—The key database is a key store used for signing, verification, encryption, and decryption between a SOA Security Manager consuming authority and a SOA Security Manager producing authority. The key database is required only if you:
  • Plan on using features related to CA SiteMinder Federation Security Services.
  • Plan on using the SOA Security Manager agent for Sharepoint.
  • Plan on configuring a SOA Security Manager Information Card Authentication Scheme, for example, for the support of Microsoft CardSpace.

    If you decided to configure the key database during installation, you are prompted to install the default certificate authority (CA) certificates. You can add additional certificates and private keys to a key database after installation.

  Note: For more information about the key database and how to add additional certificates and private keys, see the Federation Security Services Guide.

• Audit Logs—You can store audit logs in either a relational database or a text file. After you install the Policy Server, audit logging is set to a text file and not to ODBC by default.

Note: For a list of supported CA and third-party components, refer to the SOA Security Manager r12.1 SP3 Platform Support Matrix on the Technical Support site.

More information:

Locate the SOA Security Manager Platform Support Matrix