Oracle® Fusion Middleware Release Notes for Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) Part Number E28975-02 |
|
|
PDF · Mobi · ePub |
This chapter provides information about downloading the Directory Server Enterprise Edition software, and lists the primary installation requirements.
This chapter covers the following topics:
You can download the Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) software from the Oracle Software Delivery Cloud site as follows:
Point your browser to the Oracle Software Delivery Cloud site at http://edelivery.oracle.com
.
Select the required language and click Continue.
Complete the Export Validation form and click Continue.
On the Media Pack Search page:
Select Oracle Fusion Middleware from the Select a Product Pack list.
Select the required platform and click Continue.
Select "Oracle Fusion Middleware 11g Media Pack" and click Continue.
Caution:
A common mistake is to select "Oracle Fusion Middleware Identity Management 11g Release 2."
Be sure to select "Oracle Fusion Middleware 11g Media Pack."
Select Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) and click Download.
Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) is available in a zip distribution for all supported platforms.
Note:
Identity Synchronization for Windows version 6.0 SP1 is bundled with Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0).
Before you install Identity Synchronization for Windows version 6.0 SP1, you must readOracle Identity Synchronization for Windows 6 SP1 Release Notes.
For detailed information regarding hardware and operating system requirements, see the ODSEE Certification Matrix (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
).
Note:
On Linux x64 platforms, ODSEE requires x86 libraries.
The key software dependency requirements are as follows:
Directory Server Enterprise Edition 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.
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.
To update the JRE as delivered by the Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) software, you can replace the install-path/dsee7/jre
directory with the jre
directory from either a newer JDK or JRE distribution. Note that doing so will delete the jstack
utility, and only newer JAVA updates than originally delivered are supported.
This procedure will allow you to apply JAVA patches without waiting for a new version of the product.
The following dependencies may also apply in your deployment:
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.
JDBC Data Source | JDBC Driver |
---|---|
DB2 v9 |
IBMDB2 JDBC Universal Driver Architecture 2.10.27 |
Microsoft SQL Server 2005 |
sqljdbc.jar 1.2.2323.101 |
MySQL 5.x |
MySQL-AB JDBC Driver mysql-connector-java-5.0.4 |
Oracle 10gDatabase |
Oracle JDBC driver 10.2.0.2.0 |
JavaDB 10.5.3.0 |
ApacheDerbyNetwork Client JDBC Driver 10.5.3.0 |
Each Directory Server Enterprise Edition 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.
You can install Directory Server Enterprise Edition without special privileges. For more information, see the Installation Guide for Oracle Directory Server Enterprise Edition.
The ODSEE distribution includes the schema file FusionAppsSchema.ldif
, but it is not loaded by default. Before you can use ODSEE with Oracle Fusion applications, you must import the schema definitions contained in FusionAppsSchema.ldif
. For example:
# dsee7/dsrk/bin/ldapmodify -D cn=admin,cn=Administrators,cn=config -w - -f /path/to/FusionAppsSchema.ldif
For ODSEE 11g R1 (11.1.1.3) and earlier versions, apply the sunOneSchema.ldif
bundled with Oracle Virtual Directory.