test

Sun Java System Directory Server Enterprise Edition 6.0 Release Notes

Software Dependency Requirements

Directory Server relies on the Network Security Services, NSS, layer for cryptographic algorithms. NSS has been validated to work with the Sun cryptographic framework provided on Solaris 10 systems, which supports cryptographic acceleration devices.

On Windows systems, Directory Server requires ActivePerl software to use account activation and manual schema replication commands. Directory Server Enterprise Edition does not provide ActivePerl. The dependency concerns the following commands.

Directory Proxy Server requires a Java runtime environment, JRE, version of at least 1.5.0_09 on Solaris, Red Hat and Windows systems and 1.5.0_03 on HP-UX systems. The zip distribution installs JRE. When you install from the zip distribution with the JAVA_HOME environment variable set, the Java runtime environment specified by JAVA_HOME is used. If JAVA_HOME is set for your environment, make sure the version is up to date.

Directory Proxy Server has been validated with the following JDBC data sources, using the drivers provided with the software.

On Windows systems, the dsee_deploy command cannot properly register software with the Common Agent Container, cacao, when you run the command from an MKS shell. This can occur when your MKS PATH does not include the system-drive:\system32 folder. Alternatively, run the command on the Windows native command line.

Although Part II, Installing Identity Synchronization for Windows, in Sun Java System Directory Server Enterprise Edition 6.0 Installation Guide lists support only for Directory Server 6.0, Identity Synchronization for Windows directory server connectors do support Directory Server 5.2 Patch 5.

Before you can install Identity Synchronization for Windows, you must install the prerequisite Sun Java System software components, including JRE and Message Queue.

On Windows systems, the JRE installed with Console and Administration Server does not include fixes for daylight savings time changes. You must apply fixes for daylight savings time changes after installation. To fix the JRE, use the tzupdater tool, described at http://java.sun.com/javase/tzupdater_README.html. The JRE to fix is found after installation under ServerRoot/bin/base/jre/ where you installed the Console and Administration Server.

You can run Identity Synchronization for Windows in a firewall environment. The following sections list the server ports that you must expose through the firewall.

Identity Synchronization for Windows Message Queue Requirements in a Firewall Environment

By default, Message Queue uses dynamic ports for all services except for its port mapper. To access the Message Queue broker through a firewall, the broker should use fixed ports for all services.

After installing the core, you must set the imq.<service_name>.<protocol_type>.port broker configuration properties. Specifically, you must set the imq.ssljms.tls.port option. Refer to the Message Queue documentation for more information.

Identity Synchronization for Windows Installer Requirements in a Firewall Environment

The Identity Synchronization for Windows installer must be able to communicate with the Directory Server acting as the configuration directory.

Identity Synchronization for Windows Core Component Requirements in a Firewall Environment

The Message Queue, system manager, and command line interface must be able to reach the Directory Server where the Identity Synchronization for Windows configuration is stored.

Identity Synchronization for Windows Console Requirements in a Firewall Environment

The Identity Synchronization for Windows console must be able to reach the following:

Identity Synchronization for Windows Connector Requirements in a Firewall Environment

All connectors must be able to communicate with Message Queue.

In addition, the following connector requirements must be met.

Identity Synchronization for Windows Directory Server Plug-in Requirements in a Firewall Environment

Each Directory Server plug-in must be able to reach the Directory Server connector’s server port, which was chosen when the connector was installed. Plug-ins that run in Directory Server Master replicas must be able to connect to Active Directory’s LDAP, port 389, or LDAPS, port 636. The plug-ins that run in other Directory Server replicas must be able to reach the master Directory Server LDAP and LDAPS ports.