Sun OpenDS ^TM Standard Edition (SE) 1.0 is the newest member of the Sun Directory Server family of products. This directory server includes an LDAP core that is designed for easy installation, embedding, and configuration.

Sun OpenDS SE 1.0 is a high-performance, highly-extensible, pure Java directory server that delivers a fully compliant LDAPv3 server that passes all of the compliance, interoperability and security tests suites. Furthermore, Sun OpenDS SE 1.0 implements most of the standard and experimental LDAP extensions defined in the IETF as RFCs or Internet-Drafts, ensuring maximum interoperability with LDAP client applications.

With a limited footprint allowing the server to be embedded in other Java applications, OpenDS has a very rich set of APIs making it easy to extend and increase usage scope.

Sun OpenDS SE 1.0 also supports a multi-master replication model that guarantees the high availability of the data for all operations, searches or updates. While theoretically unlimited with regards to the number of masters, the Sun OpenDS SE 1.0 server has been stressed under heavy and durable load with 4 Masters.

Sun OpenDS SE 1.0 includes :

• A 6 steps graphical installation tool that allows to have a server configured, up and running in less than 3 minutes.
• A graphical status panel
• A rich command line tool to perform all online administrative tasks both interactively or scripted.
• Advance security and password policies
• Advance backup and restore capabilities.
• A complete user documentation set.

Note that the defaults settings for the Sun OpenDS SE 1.0 server are targeted for the initial evaluator or developer, running on a machine with a limited amount of resources. So it is important to do initial tuning of the Java VM and the Sun OpenDS SE server to scale. The first recommendation is to use the latest version of the Java VM (as of today Java 6 update 6 aka 1.6.0_06).

Some recommendations for the Java VM settings have been published on the Sun OpenDS SE 1.0 Documentation Wiki https://wikis.sun.com/display/SunOpenDSSEdocs/Tuning+Performance. More specifically, in order to have constant performance, tuning the Garbage Collector is needed. We recommend the CMS GC or ParallelGC. Finally, Sun OpenDS SE 1.0 does provide better performances when the database files are cached into memory. The initial size for the DB cache is 10% of the heap size and is definitely under sized. A good rule of thumb is to allocated a DB cache size about half of the heap size if the later is below or equal to 2 GB, and for heap size greater than 2 GB to allocate a DB cache size equal to the heap size minus 1GB.

with the exception of a partial support of RFC 4518 - International String Preparation

Copyright © 2008 Sun Microsystems, Inc. All rights reserved