Release Notes › Policy Server Release Notes › Installation and Upgrade Considerations › Upgrading a Japanese Policy Server

Upgrading a Japanese Policy Server

The r12.5 version of the Policy Server is not localized for the Japanese language. Upgrading the Policy Server to r12.5 results in a version that is not localized.

MDAC Versions

It is required that the MDAC versions installed on the client and server sides are compatible.

Note: More information exists in the Microsoft MDAC documentation.

Multi-Mastered LDAP Policy Stores

LDAP directories using multi-master technology may be used as SiteMinder policy stores. The following configuration is recommended when configuring an LDAP policy store in multi-master mode:

• A single master should be used for all administration.
• A single master should be used for key storage.

  This master does not need to be the same as the master used for Administration. However, we recommend that you use the same master store for both keys and administration. In this configuration, all key store nodes should point to the master rather than a replica.

  Note: If you use a master for key storage other than the master for administration, then all key stores must use the same key store value. No key store should be configured to function as both a policy store and a key store.

• All other policy store masters should be set for failover mode.

Due to possible synchronization issues, other configurations may cause inconsistent results, such as policy store corruption or Agent keys that are out of sync.

Contact SiteMinder Support for assistance with other configurations.

Multi–Mastered LDAP User Store Support Limitations (53677)

The multi–mastered LDAP enhancement has the following limitations:

• The Policy Server only supports multi–mastered user stores in a backup capacity. Because Password Services makes frequent writes to the user store, you cannot simultaneously update user information in multiple master instances. In addition, the LDAP implementation could produce out–of–date information or data loss due to delayed replication.
• Multi–mastered support does not extend to custom code such as custom authentication schemes.

Compatibility with Other Products

To ensure interoperability if you use multiple products, such as CA Identity Manager and SOA Security Manager check the Platform Support Matrices for the required releases of each product. The platform matrices exist on the Technical Support site.

Updated snmptrap File

This release includes an updated snmptrap.conf file. Before installation, back up and save the original snmptrap.conf file, located in siteminder_installation\config.

Windows Considerations

The following considerations apply to supported Windows operating environments:

DEP Error during Policy Server Installation

Symptom:

A Data Execution Prevention (DEP) error can prevent the Policy Server from installing on Windows 2008 SP2.

Solution:

1. Configure DEP for essential Windows programs and services only.
2. Run the Policy Server installer.

To configure DEP for essential programs and services

1. Right–click My Computer and select Properties.

   The System Properties dialog appears.

2. Click Advanced.

   The Advanced tab opens.

3. Under Performance, click Settings.

   The Performance Options dialog appears.

4. Click Data Execution Prevention and select Turn on DEP for essential Windows programs and services only.
5. Click OK.

   A message prompts you to restart the system.

Note: After you have successfully installed the Policy Server, you can revert the DEP settings for all programs and services.

Windows Server 2008 System Considerations

For Windows Server 2008, the User Account Control feature helps prevent unauthorized changes to your system. When the User Account Control feature is enabled on the Windows Server 2008 operating environment, prerequisite steps are required before doing any of the following tasks with a SiteMinder component:

• Installation
• Configuration
• Administration
• Upgrade

Note: For more information about which SiteMinder components support Windows Server 2008, see the SiteMinder Platform Support matrix.

To run SiteMinder installation or configuration wizards on a Windows Server 2008 system

1. Right–click the executable and select Run as administrator.

   The User Account Control dialog appears and prompts you for permission.

2. Click Allow.

   The wizard starts.

To access the SiteMinder Policy Server Management Console on a Windows Server 2008 system

1. Right–click the shortcut and select Run as administrator.

   The User Account Control dialog appears and prompts you for permission.

2. Click Allow.

   The Policy Server Management Console opens.

To run SiteMinder command–line tools or utilities on a Windows Server 2008 system

1. Open your Control Panel.
2. Verify that your task bar and Start Menu Properties are set to Start menu and not Classic Start menu.
3. Click Start and type the following in the Start Search field:

   Cmd
   

4. Press Ctrl+Shift+Enter.

   The User Account Control dialog appears and prompts you for permission.

5. Click Continue.

   A command window with elevated privileges appears. The title bar text begins with Administrator:

6. Run the SiteMinder command.

More information:

Contact CA Technologies

Deploying SiteMinder Components

If you are deploying SiteMinder components on Windows 2008 SP2, we recommend installing and managing the components with the same user account. For example, if you use a domain account to install a component, use the same domain account to manage it. Failure to use the same user account to install and manage a SiteMinder component can result in unexpected behavior.

Solaris Considerations

The following considerations apply to Solaris.

Solaris 10 Support

The Policy Server and Web Agent are certified for global and non-global zones.

Note: More information on Solaris 10 support exists in the Policy Server Installation Guide.

Errors in the SMPS Log due to a gethostbyname() Error (54190)

Network connectivity errors appear in the smps log when gethostbyname() is called. These errors appear even though the directories are available on the network. This was a Solaris issue, which according to Sun bug ID 4353836, has been resolved.

Sun lists the following patches for Solaris 9:

Solaris 9

• 112874-16 (libc)
• 113319-12 (libnsl)
• 112970-05 (libresolv)
• 115545-01 (nss_files)
• 115542-01 (nss_user)
• 115544-01 (nss_compat)

Upgrading a Solaris Policy Server (57935)

Symptom:

If your license file is older than January 2005, the Policy Server may experience problems reading the license file after an upgrade. You may receive a message stating that a valid end-user license cannot be found.

Solution:

Contact Technical Support, and request a new license file.

Report Server Required Patch Clusters

The Policy Server Installation Guide contains the system requirements required to install the Report Server. SAP BusinessObjects Enterprise provides additional patch specifications. Before installing the Report Server:

1. Go to temporary_location/docs.

   temporary_location

   Specifies the location to which you copied the installation media.

2. Open SAP BusinessObjects Enterprise XI 3.1 SP3 for Solaris – Supported Platforms (supported platforms SP3 - Solaris.pdf).
3. Review the Solaris 9 or 10 patch requirements.

Use this resource for Solaris 9 and 10 patch requirements only. This document also provides supported operating system and hardware requirements that SiteMinder does not support. For supported operating systems, see the SiteMinder r12.5 Platform Support Matrix. For system requirements, see the Policy Server Installation Guide.

Red Hat Enterprise Linux AS and ES Considerations

The following considerations apply to Red Hat Enterprise Linux AS and ES.

Red Hat Enterprise Linux AS Requires Korn Shell (28782)

A Policy Server installed on Red Hat AS requires the Korn shell. If you do not install a Korn shell on Red Hat AS, you cannot execute the commands that control the Policy Server from a command line, such as start-all and stop-all.

Excluded Features on Red Hat Enterprise Linux AS

The following features are not supported by the Policy Server on Red Hat AS:

• Safeword authentication scheme
• SiteMinder Test Tool

Apache 2.0 Web Server and ServletExec 5.0 on Red Hat Enterprise Linux AS (28447, 29518)

To use Apache 2.0 Web Server and ServletExec 5.0 on Red Hat AS

1. Run the ServletExec 5.0 AS installer against Apache 1.3.x.

   The ServletExec AS Java instance is created.

2. Run ServletExec and Apache 1.3.x, and make sure you can run /servlet/TestServlet.
3. Shutdown Apache 1.3.x, but leave ServletExec running.
4. Using anonymous FTP, access ftp://ftp.newatlanta.com/public/servletexec/4_2/patches and download the latest zip.
5. Extract the following from the zip:

   mod_servletexec2.c
   

6. Edit the httpd.conf file of your HP-Apache 2.x so that it contains the necessary ServletExec-specific directives.

   Note: The directives are also present in the httpd.conf file of your Apache 1.3.x if you allowed the ServletExec installer to update the httpd.conf during installation. For more information on editing the httpd.conf file, refer to the New Atlanta Communication ServletExec documentation.

7. Start Apache 2.x.
8. Test the Web Server with ServletExec by accessing:

   /servlet/TestServlet
   

Report Server Required Patch Clusters

The Policy Server Installation Guide contains the system requirements required to install the Report Server. SAP BusinessObjects Enterprise provides additional patch specifications. Before installing the Report Server:

1. Go to temporary_location/docs.

   temporary_location

   Specifies the location to which you copied the installation media.

2. Open SAP BusinessObjects Enterprise XI 3.1 SP3 for Linux – Supported Platforms (supported platforms SP3 - Linux.pdf).
3. Review the Red Hat 5 patch requirements.

Use this resource for Red Hat 5 requirements only. This document also provides supported operating system and hardware requirements that SiteMinder does not support. For supported operating systems, see the SiteMinder r12.5 Platform Support Matrix. For system requirements, see the Policy Server Installation Guide.