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

Run the Installer to Install the Policy Server

You run the SOA Security Manager installer (ca-soasm-12.1-cr001-win32.exe) to install the Policy Server. The executable can be downloaded from the Technical Support site.

To locate installation kits on the Support site

1. Click Technical Support.
2. Log into CA Support Online.
3. Click Download Center.
4. Search the Download Center for the installation kit you need.

Note: Before installing the Policy Server, ensure that the system meets the windows requirements.

To run the SOA Security Manager installer to install the Policy Server

1. Exit all applications that are running.
2. Navigate to where the installation executable is located.
3. Double-click ca-soasm-12.1-cr001-win32.exe.

   The SOA Security Manager installation wizard starts.

4. 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.
   • When prompted to select the components you want configured:
     • If you plan on using a relational database or an LDAP directory server other than ADAM or Sun Java System Directory Server as a policy store, deselect the Policy Store option. You manually configure a relational database or any other supported LDAP directory server after installing the Policy Server.
     • If you plan on using WS-Security SAML tokens ensure that the Create SM Key Database/Change SM Key Database Password options are selected.

     Note: If you choose to create a key database, you are prompted to install the default CA certificates. Ensure the Import default CA certificates options is selected and install these certificates. You may add additional certificates and private keys to an smkeydatabase after installation. More information on the role of smkeydatabase exists in the Policy Configuration Guide.

   • 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 SOA Security Manager. This account:
     • is the default Super User account for the FSS Administrative UI. This is not the administrator account for the Administrative UI. You identify a separate administrator account when installing the Administrative UI.
     • is used for all tasks that do not require direct access to the Administrative UI.
   • If you are using IPv6 addresses, ensure your entries include brackets.

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

   • When prompted to initialize the LDAP instance do so only to configure a new policy store instance.
   • If you cut and paste path information into the wizard, you must also enter a character before the Next button is enabled.
5. Review the installation settings and proceed.

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

   Note: The FSS Administrative UI was installed during the Policy Server upgrade. The FSS Administrative UI is for managing CA SiteMinder Federation Security Services. Register the FSS Administrative UI with the Policy Sever after upgrading the policy store. More information on registering the FSS Administrative UI exists in Registering the Federation Security Services UI.

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

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 the SOA Security Manager is installed.