The Sun OpenDS Standard Edition 2.2 software has some limitations that might affect the initial deployment of your directory server. Follow the recommendations for deployments in this section.
Administrators also should appropriately tune the Sun OpenDS Standard Edition directory server and its Java Virtual Machine (JVMTM) to ensure that adequately sized hardware is made available to support heavy write operations. For more information, see Configuring the JVM, Java Options, and Database Cache in Sun OpenDS Standard Edition 2.2 Installation Guide.
The Sun OpenDS Standard Edition directory server provides full LDAP v3 support, except for alias dereferencing, and limited support for LDAPv2.
Account lockout is supported in a single-server environment only.
Sun OpenDS Standard Edition 2.2 is not fully integrated with the Windows environment. However, it can be run as a service and is therefore displayed in the Windows Services Control Panel.
Sun OpenDS Standard Edition 2.2 provides a subset of the features that are available in Sun Directory Server Enterprise Edition. Sun OpenDS Standard Edition is constantly evolving and is expected to converge with Sun Directory Server Enterprise Edition in a future release. A replication mechanism between the two products will also be provided in a future release.
Although the Sun OpenDS Standard Edition software has been designed for n-way multi-master replication, testing has focused on up to eight replication servers in a topology.
It is recommended that you start with a clean installation of the Sun OpenDS Standard Edition 2.2 software, rather than upgrading from Sun OpenDS Standard Edition 2.0.
To maximize performance when running the server as a proxy, you should restrict queries so that the proxy returns only the required attributes rather than all the attributes of an entry.
Although all of the Sun OpenDS Standard Edition components have undergone extensive testing, the global index catalog feature of the proxy server is a relatively new feature. As such, it has not been subject to validation and testing across a variety of deployments. The specific known limitations of the global index feature are described in Known Issues When Using the Sun OpenDS Standard Edition Proxy.
The Sun OpenDS Standard Edition directory server provides better performance when the database files are cached entirely into memory.
To fully benefit from the testing of the Sun OpenDS Standard Edition software, use the Solaris 10 or Linux operating systems.
The default settings of the Sun OpenDS Standard Edition directory server are targeted initially at evaluators or developers who are running equipment with a limited amount of resources. For this reason, you should tune the Java virtual machine (JVM) and the directory server itself to improve scalability and performance, particularly for write operations. For more information, see Configuring the JVM, Java Options, and Database Cache in Sun OpenDS Standard Edition 2.2 Installation Guide.
If you update the password policy in a replicated environment, make sure to update the password policy on all of the directory servers in the topology.
Due to a limitation of the GUI setup import feature, the GUI setup can import a maximum of 2000 entries at a time. To import more than 2000 entries, use the setup utility to perform the initial configuration and then use the import-ldif utility to import the remaining data.
Importing large LDIF files by using the import-ldif command requires that you use the --skipDNvalidation option. However, if you are not certain that the LDIF file is valid, using this option is not advised.