Installation Guides › Policy Server Installation Guide › Installing the Policy Server on UNIX Systems › How to Install the Policy Server › Install the Policy Server in GUI Mode

Install the Policy Server in GUI Mode

You install the Policy Server using the SOA Security Manager installation media on the Technical Support site. Consider the following:

• Depending on your permissions, you may need to add executable permissions to the install file by running the following command:

  chmod +x installation_media
  

  installation_media

  Specifies the Policy Server installer executable.

• If you execute the Policy Server installer across different subnets, it can crash. Install the Policy Server directly on the host system to avoid the problem.

To install the Policy Server

1. Be sure that the system meets the UNIX requirements.
2. Exit all applications that are running.
3. Open a shell and navigate to the installation media.
4. Enter the following command:

   sh ./installation_media gui
   

   installation_media

   Specifies the SOA Security Manager installer 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.

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: If you are installing the Policy Server for the first–time on this system, do not configure a web server or the OneView Monitor GUI. You are installing the Policy Server using the smuser UNIX account. The installer modifies the web server configuration files, for which the smuser account does not have the appropriate root privileges. When the Policy Server installation is complete, run the Policy Server Configuration Wizard as root to configure the web server for the FSS Administrative UI or the OneView Monitor GUI.

     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 key database, you are prompted to install the default CA certificates. Leave the Import default CA certificates selected and install these certificates.

   • The installation fails if the install path you provide includes space characters. For example, "/CA/SOA SM" results in failure.
   • 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.
   • 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: The installation can take several minutes.

7. Click Done.

   The installer closes.

   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

Registering the Federation Security Services Administrative UI

Troubleshoot the Policy Server Installation