Previous Topic: Considerations for Localized InstallationsNext Topic: Application Objects in the FSS Administrative UI


Installation Media Names

The following tables identify the installation executables for the following SiteMinder components:

Note: The tables are organized by platform. For more information about supported operating systems, see the r12.0 SP3 SiteMinder Platform Support Matrix on the Technical Support site.

Documentation

The SiteMinder bookshelf is available on the Support site. There is no documentation installer. For more information, see Locate the Bookshelf.

Policy Server

Platform

Installation Executable

Linux

ca-ps-12.0-sp3-cr-linux.bin

Solaris

ca-ps-12.0-sp3-cr-sol.bin

Windows

ca-ps-12.0-sp3-cr-win32.exe

cr

Specifies the cumulative release number. The base r12.0 SP3 release does not include a cumulative release number.

Important! If you are running this wizard on Windows Server 2008, run the executable file with administrator permissions. Use these permissions even if you are logged in to the system as an administrator. For more information, see the release notes for your SiteMinder component.

Administrative UI

Platform

Installation Executable

Linux

  • (Prerequisite) adminui-pre-req-12.0-sp3-cr-linux.bin
  • (Administrative UI) ca-adminui-12.0-sp3-cr-linux.bin

Solaris

  • (Prerequisite) adminui-pre-req-12.0-sp3-cr-sol.bin
  • (Administrative UI) ca-adminui-12.0-sp3-cr-sol.bin

Windows

  • (Prerequisite) adminui-pre-req-12.0-sp3-cr-win32.exe
  • (Administrative UI) ca-adminui-12.0-sp3-cr-win32.exe
cr

Specifies the cumulative release number. The base r12.0 SP3 release does not include a cumulative release number.

Important! If you are running this wizard on Windows Server 2008, run the executable file with administrator permissions. Use these permissions even if you are logged in to the system as an administrator. For more information, see the release notes for your SiteMinder component.

Report Server

Platform

Installation Executable

Solaris

  • (Report Server) cabiinstall.sh
  • (Report Server Configuration Wizard) ca-rs-config-12.0-sp3-cr-sol.bin

Windows

  • (Report Server) cabiinstall.exe
  • (Report Server Configuration Wizard) ca-rs-config-12.0-sp3-cr-win32.exe
cr

Specifies the cumulative release number. The base r12.0 SP3 release does not include a cumulative release number.

Important! If you are running this wizard on Windows Server 2008, run the executable file with administrator permissions. Use these permissions even if you are logged in to the system as an administrator. For more information, see the release notes for your SiteMinder component.

More information:

Locate the Platform Support Matrix

ETPKI Library Installation

The Policy Server and Web Agent installations include a CA ETPKI library.

For Windows operating environments, if a CA ETPKI library exists on the machine to which you are installing the Policy Server or Web Agent, the installer upgrades the existing ETPKI library to the version shipped with the component. The CA ETPKI library remains in its current location.

For UNIX operating environments, the installer will install the CA ETPKI library to the installation_location/ETPKI directory, even if another CA ETPKI library exists elsewhere on the UNIX file system.

Upgrading a Collocated Policy Server and Web Agent

Valid on Windows

Symptom:

If a Policy Server and Web Agent are installed to the same host system, after you upgrade the Policy Server, the IIS web server fails to start and an error is logged in the Event Viewer.

Solution:

Upgrade the Web Agent. The IIS web server starts after you upgrade the Web Agent.

Policy Server Upgrade Creates a New JVMOptions File

During a Policy Server upgrade, the existing JVMOptions.txt file is renamed to JVMOptions.txt.backup. A new JVMOptions.txt file is created.

If the original file included customized parameters, be sure to modify the newly created file to include these customized parameters.

Connection Between PS on UNIX and SQL Server

When attempting to connect a SiteMinder Policy Server on Red Hat or Solaris to a Microsoft SQL Server 2008 database, you should correctly define the paths to the TraceFile, TraceDll and InstallDir parameters specified in the [ODBC] section of the system_odbc.ini file. Failure to do so may result in connectivity errors.

Character Restriction for Passwords in Installations (72360)

When installing the Policy Server, the CA Report Server, and the Administrative UI, you are asked to specify passwords for various components. Consider the following:

Policy Server

When entering password information, do not use the following characters as they are reserved or restricted:

CA Report Server

When entering password information, do not use the following characters as they are reserved or restricted:

Administrative UI

When entering password information, do not use the following characters as they are reserved or restricted:

Distributed CA Directory Server Policy Store

If you are using multiple DSAs to function as a policy store, ensure that host information of the router DSA is listed first in the Policy Server Management Console. If you do not list the router DSA host information first, an error occurs when you attempt to install the policy store data definitions.

Note: For more information on configuring CA Directory Server as a policy store, refer to the Policy Server Installation Guide.

Importing Event Handler Libraries

Consider the following before upgrading a Policy Sever to r12.0 SP3:

  1. Open the Policy Server Management Console and click the Advanced Tab.
  2. In the Event Handlers field, replace the path to the current event handler library with the path to the XPSAudit event handler library.

    Note: The default location of the XPSAudit event handler library is policy_server_home\bin.

    policy_server_home

    Specifies the Policy Server installation path.

  3. Click Apply.

    The path to the event handler library is saved. The Event Handlers field appears disabled.

    Note: By default, the only event handler library that appears in the Advanced tab is XPSAudit.dll.

  4. Use the XPSConfig utility to set additional event handler libraries, previously used or otherwise, to the XPSAudit list.

    Note: More information on using the XPSConfig utility to set event handler libraries exists in the Policy Server Administration Guide.