The Sun OpenDS Standard Edition 2.0 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.0 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.
The Sun OpenDS Standard Edition 2.0 directory server is not integrated into the Windows graphical interface.
The Sun OpenDS Standard Edition 2.0 directory server is not currently designed to be a complete replacement for Sun Directory Server Enterprise Edition. In a future release, there will be a replication mechanism between the two products.
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.
The Sun OpenDS Standard Edition directory server provides better performance when the database files are cached entirely into memory.
To fully benefit from the extensive 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.0 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.
You cannot use the setup command to configure replDue to ication in command-line mode. After you have set up your directory servers by using setup, use the dsreplication command to initialize the directory servers in your topology.
Note - You can use the GUI setup to configure replication, if you have configured all of the directory servers in the same manner.
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.