Software Dependency Requirements

• Directory Server Enterprise Edition Software Dependency Requirements

• Supported Application Servers for Directory Service Control Center

• Supported JDBC Data Sources

• Supported Browsers for Directory Service Control Center

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

• Identity Synchronization for Windows Software Dependency Requirements

• Identity Synchronization for Windows Requirements in a Firewall Environment

Directory Server Enterprise Edition Software Dependency Requirements

The key software dependency requirements are as follows:

• 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 Microsoft Windows systems, you must disable the pop-up blocker to make Directory Service Control Center work properly.

• Directory Proxy Server will work with any LDAPv3–compliant directory server, but has been tested only with the directory server component of Directory Server Enterprise Edition.

• In Solaris 10, rc.scripts are deprecated so commands like dsadm autostart are not supported. Instead use the 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.

Supported Application Servers for Directory Service Control Center

The Directory Service Control Center supports the following application servers:

• GlassFish 3.x

• Tomcat 6.0+

• Sun Java System Web Server 7.0+

• Oracle WebLogic Server 10.3.3

• Oracle iPlanet Web Server 7.0.9

For more information, see Appendix A, Deploying the DSCC WAR File, in Oracle Fusion Middleware Installation Guide for Oracle Directory Server Enterprise Edition.

Supported JDBC Data Sources

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.

Supported Browsers for Directory Service Control Center

The following table displays the browsers for each operating system that supports Directory Service Control Center.

Identity Synchronization for Windows and 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.

Identity Synchronization for Windows Software Dependency Requirements

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

• No JRE is provided with Identity Synchronization for Windows.

  The Identity Synchronization for Windows installer requires J2SE or JRE 1.5.0_09. For more information, go to http://java.sun.com.

• Identity Synchronization for Windows requires the installation and configuration of Message Queue 4.3, which is available from Oracle Software Downloads. Select Sun Downloads A-Z Listing and navigate to Message Queue 4.3.

  Message Queue 3.7 (delivered as a Java Enterprise System shared component) is also supported.

  When you install Identity Synchronization for Windows, you must specify the path to the correct version of Message Queue. The Identity Synchronization for Windows installation program then installs a required broker into Message Queue, so that Identity Synchronization for Windows can use Message Queue for synchronization.

Identity Synchronization for Windows Requirements in a Firewall Environment

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.

Message Queue Requirements

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.

Installer Requirements

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

• If you are installing an Active Directory connector, the installer must be able to contact Active Directory’s LDAP port, 389.

• If you are installing a Directory Server connector or a Directory Server plug-in (subcomponent), the installer must be able to contact the Directory Server LDAP port, default 389.

Core Component Requirements

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.

Console Requirements

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

• Active Directory over LDAP, port 389, or LDAPS, port 636

• Active Directory Global Catalog over LDAP, port 3268, or LDAPS, port 3269

• Each Directory Server over LDAP or LDAPS

• Administration Server

• Message Queue

Connector Requirements

All connectors must be able to communicate with Message Queue.

In addition, the following connector requirements must be met.

• The Active Directory connector must be able to access the Active Directory Domain Controller over LDAP, port 389, or LDAPS, port 636.

• The Directory Server connector must be able to access Directory Server instances over LDAP, default port 389, or LDAPS, default port 636.