Contained WithinFind More DocumentationFeatured Support Resources |  Download this book in PDF (809 KB)
Software Dependency RequirementsDirectory 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 Microsoft 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. On Microsoft Windows systems, you must disable the pop-up blocker to make Directory Service Control Center work properly. The Directory Service Control Center supports the following application servers:
For more information, see Installing Directory Service Control Center From Zip Distribution in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide. Directory Proxy Server requires a Java runtime environment, JRE, version of at least 1.5.0_09 on Solaris, Red Hat and Windows 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. Ensure that the JAVA_HOME environment variable is set to use the Java 5 runtime environment, (Java 1.5). The Directory Proxy Server may hang on some systems when running in a Java 6 runtime environment, (Java 1.6). Directory Proxy Server will work with any LDAPv3 compliant directory servers, but it is tested only with Sun Java System Directory Server. For virtualization, Directory Proxy Server has been validated with the following JDBC data sources, using the drivers mentioned below. Though Directory Proxy Server works with all the JDBC 3 compliant drivers.
On Microsoft 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 Microsoft Windows native command line. On Solaris 10, rc.scripts are deprecated so commands like dsadm autostart are not supported. Instead use Solaris 10 Service Management Facility (SMF) to handle these types of requests. For example, dsadm enable-service. For more information on SMF, see the Solaris operating system documentation. 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. Identity Synchronization for Windows Requirements in a Firewall EnvironmentYou can run Identity Synchronization for Windows in a firewall environment. The following sections list the server ports that you must expose through the firewall. Message Queue RequirementsBy 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. Installer RequirementsThe Identity Synchronization for Windows installer must be able to communicate with the Directory Server acting as the configuration directory.
Core Component RequirementsThe 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. Console RequirementsThe Identity Synchronization for Windows console must be able to reach the following:
Connector RequirementsAll connectors must be able to communicate with Message Queue. In addition, the following connector requirements must be met.
Directory Server Plug-in Requirements in a Firewall EnvironmentEach 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. Supported Browsers for Directory Service Control CenterThe following table displays the browsers for each operating system that supports Directory Service Control Center.
|
||||||||||||||||||||
|