- Linux operating systems—Be sure that the required Linux libraries are installed to the Policy Server host system.
Note: For more information, see Required Linux Libraries.
- Administrator privileges—Be sure that you have created a new UNIX account and understand which components require root administrator privileges.
Note: For more information about the required administrator privileges, see How to Prepare for the Policy Server Installation.
- Free space in /tmp—The Policy Server install requires 200 MB of free space in /tmp.
- System path length—The Policy Server installation fails if the system path length exceeds 1024 characters, including or excluding the SiteMinder added directories.
Note: We recommend trimming the pre-SOA Security Manager system path to approximately 700 characters for best results.
- Web Server instance—Be sure that the Sun Java System web server instance is stopped before installing the Policy Server.
- Telnet or other terminal emulation software—If you plan on installing the Policy Server using Telnet or other terminal emulation software, install the Policy Server using a console window. The installer throws a Java exception and exits if you try to run a GUI through a telnet window.
- Exceed X-windows application—Running the Policy Server installer or the Policy Server Configuration Wizard (ca-ps-config.bin) using an Exceed X-windows application may cause text in the dialog box to truncate due to unavailable fonts using Exceed. This limitation has no affect on the Policy Server installation or configuration.
- Environment variables—The Policy Server installation modifies environment variables.
- IBM Directory Server only—Using an IBM Directory Servers in your SOA Security Manager environment requires that you edit the V3.matchingrules file by adding the following line:
MatchingRules=(2.5.13.15 NAME ‘integerOrderingMatch’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.27)
The Directory store will not be configured correctly and the necessary SiteMinder policy store objects cannot be created if the V3.matchingrules file does not contain the change.
