Release Notes › Policy Server Release Notes › Installation and Upgrade Considerations › Considerations for Localized Installations

Considerations for Localized Installations

There are a number of limitations and considerations for installations of localized versions of SiteMinder.

Consider the following before installing the SiteMinder Policy Server on a system with a non–English operating system:

• Localized versions of SiteMinder must be installed on a corresponding operating system.

  For example, you must install a Japanese version of the SiteMinder Policy Server on a Japanese operating system. A Japanese version of the Policy Server will not run properly on an English operating system.

Limitations include the following:

• SiteMinder cannot be installed using the silent installation mode in a directory with a name that uses multi-byte characters.
• The Administrative UI cannot be installed in any mode (silent, command line, GUI) in a directory with a name that uses multi–byte characters.
• Windows 2008 lets you set different regional and language settings for individual user accounts. However, the System and other service accounts must be set to use the default Japanese locale or the component you are installing will not initialize.

  To set the locale for the System or other service accounts, see the Microsoft documentation.

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.

Modify a Customized 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.

For any Apache-based agents, add the SiteMinder/resources directory to the CLASSPATH in the JVMOptions.txt file, as shown in the following example:

-Djava.class.path=C:/Program Files (x86)/CA/siteminder/resources;

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:

• (Windows only) A percent sign (%)
• (Reserved by InstallAnywhere) A dollar sign ($)
• (UNIX only) An apostrophe (’)
• (UNIX only) Quotation marks (“”)

CA Report Server

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

• (Reserved by InstallAnywhere) A dollar sign ($)
• (UNIX only) An apostrophe (’)
• (UNIX only) Quotation marks (“”)

Administrative UI

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

• (UNIX only) An apostrophe (’)
• (UNIX only Quotation marks (“”)

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.5:

• If the Policy Server Management Console Advanced tab does not contain event handler libraries, the XPSAudit event handler library (XPSAudit.dll) is added to the Event Handlers field. No further action is required.
• If the Policy Server Management Console Advanced tab does contain event handler libraries, complete the following after upgrading the Policy Server:

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.