Installation Guides › Policy Server Installation Guide › Installing the Policy Server on Windows Systems › How to Install the Policy Server › Run the Policy Server Installer

Run the Policy Server Installer

Install the Policy Server using the SOA Security Manager installation media on the Technical Support site.

Note: For a list of installation media names for each operating system, see the installation and upgrade considerations in the Release Notes.

To run the Policy Server installer

1. Verify that the system meets the Windows requirements.
2. Exit all applications that are running.
3. Navigate to the installation material.
4. Double-click installation_media.

   installation_media

   Specifies the name of the SOA Security Manager installation executable.

   Note: For a list of installation media names for each operating system, see the installation and upgrade considerations in the Release Notes.

   The SOA Security Manager installer starts.

   Important! If you are running this wizard on Windows Server 2008, run the executable file with Administrator permissions, even if you are logged into the system as an Administrator. For more information, see the Release Notes.

5. Use the gathered system and component information to install the Policy Server and configure Policy Server components. Consider the following when running the installer:
   • When prompted to select features to install, select CA SOA Security Manager Policy Server.
   • You are prompted to select a FIPS mode of operation. The use of FIPS-compliant algorithms in your environment is optional. If your organization does not require this type of encryption, install the Policy Server in FIPS-compatibility mode.
   • When prompted to select the components you want configured:
     • As detailed in Policy Store Considerations, the Policy Server installer can automatically configure a policy store. If you are using a vendor that this topic does not list or you do not have the required information, clear the Policy Store check box. You can configure the policy store manually after installing the Policy Server.
     • If you plan on generating WS-Security SAML tokens, select the Create SM Key Database/Change SM Key Database Password option.

     Note: Configuring a web server installs the FSS Administrative UI. If you do not plan on generating WS-Security SAML tokens, the FSS Administrative UI is not required.

     Note: If you decide to create a SOA Security Manager key database, you are prompted to install the default CA certificates. Leave the Import default CA certificates check box selected and install these certificates. You can add additional certificates and private keys to a key database after installation.

   • If you are initializing a policy store, you are prompted to enter a password for the default SOA Security Manager user account. The default account name is siteminder.

     Note: The dollar sign is a reserved character in InstallAnywhere. Using it is seen as the start of an InstallAnywhere variable. To have InstallAnywhere interpret the result as an actual $, you need to replace each instance with $DOLLAR$.

   • If you are using IPv6 addresses, be sure that entries include brackets.

     Example: [2001:db8::1428:57ab]

   • If you enter path information in the wizard by cutting and pasting, enter (and delete, if necessary) at least one character to enable the Next button.
6. Review the installation settings and click Install.

   The Policy Server and any selected components are installed and configured.

   Note: If you chose to install the FSS Administrative UI, register the FSS Administrative UI with the Policy Server after installing and registering the Administrative UI.

If you experience problems during the installation, you can locate the CA_SOA_Security_Manager_release_InstallLog.log file in soa_home\install_config_info

release

Specifies the SOA Security Manager release number.

You can also use the ca-ps-details.log file located in soa_home\siteminder\install_config_info to check the status of the installer's auto-configuration of an ADAM or Sun Java System Directory Server policy store.

soa_home

Specifies the path to where SOA Security Manager is installed.

More information:

Locate the Installation Media

Installation Media Names