Sun OpenDS Standard Edition 1.0 Release Notes

Preface

The Sun OpenDS Standard Edition 1.0 Release Notes contain important information to install and to configure your directory services system. The Release Notes address new features, installation procedures, configuration notes, known issues, and other information. Read this document before you begin to use the Sun OpenDS Standard Edition 1.0.

Who Should Use This Book

Anyone who installs or administers the Sun OpenDS Standard Edition software should review these notes.

Before You Read This Book

You should also be familiar with the following related topics:

• Directory server administration
• Lightweight Directory Access Protocol (LDAP)
• Java technology
• Extensible Markup Language (XML)
• Public-key cryptography and Secure Sockets Layer (SSL) protocol
• Intranet, extranet, and Internet security including the use of digital certificates

How This Book Is Organized

This book includes the following chapters.

Chapter 1, Installation Notes covers topics related to installation, including hardware and software requirements.

Chapter 2, Configuration Notes covers topics related to configuring the Simple Network Monitoring Protocol (SNMP) connection handler and the Java Virtual Machine (JVM) to optimize the directory server's performance.

Chapter 3, Related Documentation provides information to access the Sun OpenDS Standard Edition 1.0 documentation set.

Chapter 4, Sun OpenDS Standard Edition Known Issues covers known issues for the directory server at the time of its release.

Redistributable Files

The Sun OpenDS Standard Edition does not provide any files that you can redistribute.

Document Conventions

These Release Notes and the Sun OpenDS Standard Edition documentation have the following document conventions.

Symbol Conventions

The following table explains symbols that might be used in this book.

Table P-1 Symbol Conventions

Shell Prompts in Command Examples

The following table shows default system prompts and superuser prompts.

Table P-2 Shell Prompts

Documentation, Support, and Training

The Sun web site provides information about the following additional resources:

• Documentation Go to Sun OpenDS Standard Edition Documentation Center.
• Support Go to Sun Support Center.
• Training This release will not offer any training classes for users. Sun plans to offer a training class for the Sun OpenDS Standard Edition in the future.

Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.

Note - Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Third-Party Trademarks and Licenses

LINUX is a trademark of Linus Torvalds. All other third-party trademarks are the property of their respective owners.

This product includes source code for the Berkeley Database, a product of Oracle Corporation. Your use of the Berkeley Database software separately from the Sun OpenDS Standard Edition or authorized derivatives thereof is subject to additional licensing conditions.

Chapter 1 Installation Notes

The Sun OpenDS Standard Edition is a high-performance, highly-extensible, pure Java directory server that supports the Lightweight Directory Access Protocol (LDAPv3).

For specific information on installing the Sun OpenDS Standard Edition 1.0, see the Sun OpenDS Standard Edition Documentation Center.

For addition information and downloads, see the Sun OpenDS Resource Center.

What's New

The Sun OpenDS Standard Edition is the newest member of the Sun Directory Server product family. This “next-generation” directory server includes an LDAP core that is designed for performance (fast reads and writes), scalability (vertical and horizontal), robust availability, extensibility (numerous plug-in points), security, and maintenance.

The Sun OpenDS Standard Edition provides the following features:

• Full LDAPv3 compliant directory server according to RFC 4510 collection Technical Specification Road Map
• Multi-master replication (WAN support, strong authentication, encryption, conflict resolution)
• Full set of command line tools that can be run in interactive mode or run within scripts
• Graphical setup installer, uninstaller, and status panel
• Extensions (extended operations, controls, many others)
• Security (access controls, privileges, SASL, SSL, TLS, StartTLS, password and account policies)
• Monitoring (JMX, LDAP, SNMP, notifications, logs)
• Group Interfaces (static, dynamic, virtual) and schema management

Directory Server Hardware Requirements

You can configure the Sun OpenDS Standard Edition server in such a way that it uses substantially less, or more disk space depending on your application and performance needs. Any setup consideration must include the amount of memory for the directory server's runtime, database, and log files for optimized directory server performance.

As a general guideline, Sun OpenDS Standard Edition software recommends the following hardware.

Memory	Platform Requirement
RAM	For evaluation purposes only, at least 512 Mbytes–1 Gbyte of free memory is recommended. For production servers, at least 2–4 GB is recommended. Note - For large databases requiring more than 4 Gbytes of RAM, your system should use 64–bit architectures.
Local disk space	For evaluation purposes, at least 2 Gbytes of free local disk space for the binaries, logs, and database is recommended. For production servers, you should have enough disk space to hold the data, log files, and changelog database that are managed by the server. For example, logs files can grow to 1 Gbyte of memory depending on your application. The changelog DB can potentially grow up to 30–40 Gbytes with heavy loads of 1000 modifications per second.

Supported Operating Systems

The Sun OpenDS Standard Edition software is supported on the following platforms.

Table 1-1 Supported Operating Systems

Note - x64 means both Intel 64 and AMD 64.

Operating System Requirements

Operating System Requirements	Header
Operating System TCP/IP Ports	The Sun OpenDS Standard Edition uses the following ports by default: * LDAP, default port 389 * LDAPS, default port 636 * SNMP, default port 161 if configured * JMX, default port 1689 * Replication port 8989 Note - The ports can differ between root and non-root users for some protocols.
File Descriptor Limits	On some Linux systems, the default file descriptor limit is set to 1024. This value might be too small when processing the total number of client connections, database files, and log files that Sun OpenDS Standard Edition requires to operate. It is strongly recommended that this file descriptor limit be increased to 64K or (65536 field descriptors).

Java Requirements

The Sun OpenDS Standard Edition directory server requires that your system have an installed version of at least Java Standard Edition 5 (Java SE 5) with the minimum Java runtime environment (JRE) version number 1.5.0_08. Only Sun Java SE versions of the JRE for 32 bit and 64 bit architectures are supported at this time.

For improved performance and better tool and diagnostic support, use the latest version of Java SE 6.

Java SE runtime environments for Solaris, Linux, and Windows systems are available online at the following web site: http://java.sun.com/javase/downloads.

Software Environment Limitations and Recommendations

The Sun OpenDS Standard Edition 1.0 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 (JVM) to ensure that adequately sized hardware is made available to support heavy write operations. Review the recommendations to tune the directory server, particularly of the JVM, in Chapter 2, Configuration Notes.

Sun OpenDS Standard Edition Limitations

• Sun OpenDS Standard Edition provides full LDAP v3 support, except for alias dereferencing and Internationalized String Preparation, and limited support for LDAPv2.
• Account lockout only works in a single server environment.
• Sun OpenDS Standard Edition 1.0 is not integrated into the Windows graphical interface.
• Sun OpenDS Standard Edition is currently not designed to be a complete replacement for Directory Server Enterprise Edition. In a future release, there will be a replication mechanism between the two products.
• QuickSetup Welcome screen has incorrect links to Sun OpenDS SE documentation site. Point your web browser to the Sun OpenDS Standard Edition Documentation Center.
• The Sun OpenDS Standard Edition has no uninstall utility for its root product files. You must remove the root directory manually.
• Although the Sun OpenDS Standard Edition has been designed for n-way multi-master replication, testing has focused on up to four replication servers in a topology at this time.
• Although Sun supports French, German, Spanish, Japanese, Korean, Simplified Chinese, and Traditional Chinese, some utilities and messages are not fully localized. Full user interface messages will be localized in the next Sun OpenDS Standard Edition release.
  • The status, uninstall, dsreplication command line utilities are localized.
  • The dsconfig, ldapmodify, ldapsearch command line utilities are partially localized.
  • The uninstall, dsconfig, dsreplication, and start-ds help pages are localized.
  • Some log messages are localized when starting and stopping the directory server.

    Note - The localized commands can produce English messages, because they are generated by different parts of the Sun OpenDS Standard Edition code or because some messages were added after the translation was delivered.

  • Locale-based collation rules are not supported.
  • The ldapsearch --sortOrder or -S option does not sort according to the user locale.

Sun OpenDS Standard Edition Recommendations

• Sun OpenDS Standard Edition provides better performance when the database files are cached entirely into memory.
• When moving entries, name-conflicts can arise in multi-master replication topologies. To minimize these name-conflicts, the provisioning (adding) and deprovisioning (deleting) of users must be done on a single master with a failover to another directory server if needed. Searches and modifications can be load-balanced between all of the directory servers.
• To fully benefit from the extensive testing of the Sun OpenDS Standard Edition, use the Solaris 10 or Linux operating systems.
• The default setting of the Sun OpenDS Standard Edition is targeted initially for 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 Sun OpenDS Standard Edition to improve scalability and performance, particularly for write operations. See the section on Configuring Java Virtual Machine Options for more information.
• 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.
• The setup utility does not allow you to set up replication in interactive mode. After you have set up your directory servers by using setup, use the dsreplication utility to initialize the directory servers in your topology.

  Note You can use the setup utility in GUI mode to set up your replication servers if you have configured all of the directory servers in the same manner.

• Due to a limitation of the GUI setup import feature, import 2000 entries or less at one time. For imports larger than 2000 entries, use the setup utility to perform the initial configuration and then use the import-ldif utility to import the remaining data.

Getting the Software

You can get the Sun OpenDS Standard Edition 1.0 software by using one of the following methods:

• You can download the software by means of a zip compressed archive from Sun OpenDS Downloads. The zip distribution is a stand-alone delivery method to install and to configure a Sun OpenDS Standard Edition directory server instance. The installation process for the directory server is very simple. Download the zip file, and then extract the contents of this zip file to the location where you want to install the server.
• You can install the software from the Sun OpenDS Standard Edition Media Kit (part number: DSS99–100–9929). Run the setup.sh command from the CD or copy the zip file to a folder, and extract the contents of this zip file to the location where you want to install the server.

Note - You can install directory server from the zip compressed archive or from the Media Kit CD without special privileges.

To Download the Sun OpenDS Standard Edition Software

1. Point your browser to Sun OpenDS Downloads.
2. Click Sun Download Center, and follow the instructions to save the zip file locally on your computer.
3. Unzip the zip compressed archive file.

   $ unzip SunOpenDS_SE1.0.zip
   

   
   If your system does not come with a utility for extracting zip archives, you can use the jar tool that is provided with the Java environment.

   $ /usr/java/bin/jar -xvf SunOpenDS_SE1.0.zip
   

4. Change to the SunOpenDS_SE1.0 subdirectory.

   $ cd SunOpenDS_SE1.0
   

5. View the SunOpenDS_SE1.0 subdirectory.

   (UNIX,Linux)    $ ls
   (Windows)       C:\> dir
   
   ./           Legal/       setup/       setup.sh*
   ../          README.txt   setup.bat
   

To Obtain the Sun OpenDS Standard Edition Software from the Media Kit

1. Insert the Media Kit CD into your cdrom drive.
2. Change to the CD directory.
   For example, assume that you have mounted your CD on /vol/cdrom on UNIX or Linux systems, or the E: drive on Windows systems.

   (UNIX,Linux)   $ cd /vol/cdrom
   (Windows)      E:\> cd /cdrom
   

3. At the root directory of the CD, you see the following files:

   (UNIX,Linux)   $ ls
   (Windows)      E:\> dir
   
   ./           Legal/       setup/       setup.sh*
   ../          README.txt   setup.bat
   

4. (Optional) If you prefer to copy the directory to your computer first, use the following commands.

   (UNIX,Linux)   $ cd /vol/cdrom
                  $ mkdir /tmp/sunopends
                  $ cp -r * /tmp/sunopends
   
   (Windows)      E:\> cd /cdrom
                  E:\> XCOPY E:\*.* /sunopends
   

To Install the Sun OpenDS Standard Edition Directory Server

1. From the top level of the installation directory (SunOpenDS_SE1.0) or from the Media Kit CD, type:

   (UNIX,Linux)    $ ./setup.sh
   (Windows)       C:\> setup.bat
   

   Note - You can also use setup in command-line mode. Type ./setup.sh --cli on UNIX or Linux systems, or setup.bat --cli on Windows systems.

2. Read the software licensing agreement, and click Accept.
   If you cannot read the software licensing agreement, change to the Legal subdirectory, and open the license file in your preferred language.
3. On the Select Install Directory dialog box, select the path where you want to install Sun OpenDS Standard Edition, and click INSTALL.
   When the installation has completed, click OK on the dialog box.
4. From the path where you installed Sun OpenDS Standard Edition, change to the opends subdirectory.

   (UNIX, Linux)  $ cd opends 
   (Windows)      C:\> cd opends   
   

5. View the contents of the subdirectory.

   (UNIX, Linux)  $ ls 
   (Windows)      C:\> dir
   ./                 ../       Legal/          OpenDS-1.0.0.zip   addons/    
   

6. Unzip the zip file.

   $ unzip OpenDS-1.0.0.zip
   

7. View the contents of the subdirectory.
   You should see the OpenDS-1.0.0 directory.

   (UNIX, Linux)  $ ls 
   (Windows)      C:\> dir
   ./         ../     Legal/      OpenDS-1.0.0.zip   addons/   OpenDS-1.0.0/ 
   

8. After you have unpacked the Sun OpenDS Standard Edition, change to the installation subdirectory.

   (UNIX, Linux)  $ cd OpenDS-1.0.0 
   (Windows)      C:\> cd OpenDS-1.0.0
   

9. Type setup to configure your directory server.
   The utility launches the graphical installer.

   (UNIX, Linux)  $ setup 
   (Windows)      C:\> setup.bat
   

10. Answer the questions in the installation wizard.
    For more information, see the Sun OpenDS Standard Edition 1.0 Installation Guide.

To Uninstall the Sun OpenDS Standard Edition Directory Server

Before You Begin

Back up your files and directories. Make sure that you know how to restore the system, if necessary. For more information on running backups, see Sun OpenDS Standard Edition 1.0 Administration Guide.

1. Open a terminal window, and change to the installation subdirectory.

   (UNIX, Linux)  $ cd OpenDS-1.0.0 
   (Windows)      C:\> cd OpenDS-1.0.0
   

2. Type uninstall to remove your directory server.
   The utility launches the graphical uninstaller.

   (UNIX, Linux)  $ uninstall 
   (Windows)      C:\> uninstall.bat
   

3. Answer the questions in the Uninstaller wizard to remove the installation directory.
   For more information, see Sun OpenDS Standard Edition 1.0 Installation Guide.
4. Locate the SunOpenDS_SE1.0 directory, and manually remove the directory and its subdirectories.

   (UNIX, Linux)  $ rm -ir SunOpenDS_SE1.0 
   (Windows)      C:\> rmdir /s /q C:\path\to\SunOpenDS_SE1.0
   

Chapter 2 Configuration Notes

This section presents some important configuration notes for monitoring and optimizing performance on your directory server. This chapter contains the following sections:

• Configuring the Simple Network Management Connection Handler
• Configuring Java Virtual Machine Options

Configuring the Simple Network Management Connection Handler

The Sun OpenDS Standard Edition 1.0 directory server can be configured for monitoring through Simple Network Management Protocol (SNMP). The Sun OpenDS Standard Edition code uses the Java Dynamic Management Kit (JDMK) to create smart agents for the SNMP connection handler. To enable SNMP for your directory server, you must specify the file path for the JDMK jar file (jdmkrt.jar) that comes bundled with the Sun OpenDS Standard Edition distribution.

To Configure SNMP

1. Open a terminal window, and change to the installation directory.

   (Unix,Linux)    $ cd Sun-OpenDS-SE-installation-directory/bin
   (Windows)       C:\> cd Sun-OpenDS-SE-installation-directory\bat
   

2. Use the dsconfig command to enable SNMP for your directory server.
   For Windows systems, type the command on a single line. Be sure to specify your port and root user password.

   $ dsconfig set-connection-handler-prop \ 
     --port 1389 \ 
     --bindDN "cn=Directory Manager" \ 
     --bindPassword password \ 
     --handler-name "SNMP Connection Handler" \ 
     --set enabled:true \
     --set listen-port:8085 \ 
     --set opendmk-jarfile:Sun-OpenDS-SE-installation-directory/../addons/jdmkrt.jar \ 
     --no-prompt
   

Configuring Java Virtual Machine Options

The default setting of the Sun OpenDS Standard Edition is targeted initially for evaluators and developers who are running equipment with a limited amount of resources. For this reason, tune the Java Virtual Machine (JVM) and Sun OpenDS Standard Edition to improve scalability and performance (particularly for write operations) by using a java.properties file.

The following list summarizes useful JVM options to optimize the Sun OpenDS Standard Edition 1.0 performance. For more information, see Configuring the JVM and DB Cache.

Server Off

-server

Selects server application runtime optimizations. Sun OpenDS Standard Edition takes longer to start and “warm up” but will be more aggressively optimized to produce higher throughput.

-d64

For 64–bit machines only. This option should be specified when large JVM heaps of 4 Gbytes or larger is required in 64–bit architectures. By default, a 32–bit JVM is selected regardless of the architecture.

-Xms2G -Xmx2G

Selects the initial and maximum Java heap size. These options should be used to reserve enough room for the directory server runtime and its database cache (or caches). You should configure the JVM heap size to be as large as possible. Increasing the amount of memory available can improve performance, but increasing it to too high a value can have a detrimental effect in the form of longer pauses for full garbage collection runs. Therefore, keep the initial and maximum sizes to the same values.

As a guide, take a look at the size of the JE database folders (Sun-OpenDS-SE-installation-directory/db/userRoot). Based on the combined size, determine how much you want to cache in memory. After determining this value, tune the local database (DB) back-end properties db-cache-percent or db-cache-size and other JVM options appropriately. You must be careful to allow enough additional room for the Sun OpenDS Standard Edition runtime.

For example, if you have a single database of 1 Gbyte that you want to store entirely in memory, configure a 2 Gbyte heap with 60% reserved for the DB cache. You can test this setup by preloading the database with the local database back end by using the preload-time-limit property.

Note - JVM heaps greater than 4 Gbytes require a 64–bit JVM.

-XX:-DisableExplicitGC

Prevents external applications from forcing expensive garbage collections. If you are using jstatd or other Java Remote Method Invocation (RMI)-based applications to monitor Sun OpenDS Standard Edition, you should consider using this option to avoid unexpected pauses.

-XX:NewSize=512M

In heavy throughput environments, you should consider using this option to increase the size of the JVM young generation. By default, the young generation is quite small, but high throughput scenarios can result in a large amount of generated garbage. Excess generated garbage causes the JVM to inadvertently promote short-lived objects into the old generation.

-XX:+AggressiveOpts

Enables additional JVM optimizations, which can yield higher performance.

Server Only

-XX:+UseConcMarkSweepGC

Selects the Concurrent Mark Sweep (CMS) garbage collector (GC). This garbage collector is set to “low pause time”. This collector results in a lower average throughput for your application but has much shorter CPU-intensive garbage collections. This option is required in environments that have response time constraints.

-XX:CMSInitiatingOccupancyFraction=70

Selects the level at which the collection is started. The default value is 68%.

Offline Import Only

-XX:+UseParallelOldGC

Selects the parallel old generational garbage collector. This garbage collector is set for “high throughput”. This collector maximizes the average throughput of the import-ldif utility at the cost of an occasional stop-the-world garbage collection, which is not as critical for imports.

Other Applications

-client

Selects client application runtime optimizations. The application is faster to start and more responsive due to lower compilation overheads

-Xms8m

Selects a low initial JVM heap size for the application.

-XX:+PrintGCDetails

Prints the garbage collection details.

-XX:+PrintGCTimeStamps

Prints the garbage collection time stamps to help with debugging.

Chapter 3 Related Documentation

This section covers the available documentation for the Sun OpenDS Standard Edition Directory Server.

Accessing the Sun OpenDS Standard Edition Documentation

The following Sun OpenDS Standard Edition 1.0 documentation is available at the following site: Sun OpenDS Standard Edition Documentation Center

• Sun OpenDS Standard Edition 1.0 Installation Guide
• Sun OpenDS Standard Edition 1.0 Administration Guide
• Sun OpenDS Standard Edition 1.0 Configuration Reference Guide
• Sun OpenDS Standard Edition 1.0 Reference Guide
• Sun OpenDS Standard Edition 1.0 Command-Line Usage Guide
• Glossary of LDAP and Directory Terminology

Note - Future plans are to include the full Sun OpenDS Standard Edition documentation set on http://docs.sun.com/.

Chapter 4 Sun OpenDS Standard Edition Known Issues

The following issues exist for the release of the Sun OpenDS Standard Edition 1.0.

Known Issues

This section lists the bugs that are known to exist at the time of the release.

Issue 2606

ldif-diff causes an OutOfMemory error with large LDIF files.

Depending on the JVM memory settings, the ldif-diff utility results in a Java heap outOfMemory error if large LDIF files are loaded.
Workaround: If you experience this problem, increase the size of your Java heap memory.

Issue 2829

Problems configuring and unconfiguring replication servers.
When replication servers are configured by using the dsreplication tool, unconfigured, and then reconfigured again, the replication servers fail to connect, because they cannot locate the correct certificates.

Issue 2963

dsreplication --status sometimes returns large values for missing changes.
Under certain load conditions, the dsreplication --status command sometimes displays a large value for missing changes.

Issue 3057

JE checkpointer thread causes unchecked database growth.
An existing bug in the Oracle Berkeley Java Edition (JE) code results in the JE checkpointer thread to fail to scale under heavy write loads.
Workaround: If you experience this problem, decrease the number of worker threads and increase the number of cleaner threads in the JE back end .

Issue 3315

dsreplication --initialize-all returns before peer has completed initialization.

Issue 3328

Server is started with options -client -Xms8m when started by status-panel.
Server is started with options -client -Xms8m when started by status-panel. When stopping and then starting the directory server by using the Status Panel, the directory server starts with the wrong Java arguments.
Workaround: Do not use the status-panel for stopping or starting the server.

Issue 3376

Command output becomes garbled in non-UTF-8 locales
Sun OpenDS Standard Edition only supports UTF-8 encoding on the output. If you are using a non-UTF-8 encoding on a localized UNIX or Linux platform, make sure to set the environment to UTF-8 to prevent the international characters from being garbled. For example to switch to French locale with UTF-8 support, do the following:

$ export LC_ALL=fr_FR.UTF-8

Also, make sure your terminal emulator is set to UTF-8. Because Microsoft Windows does not support UTF–8 encoding, you are likely to see garbled characters in the localized messages if you are using a localized version of Windows. For Windows systems, you might be better off seeing messages in English. To switch Sun OpenDS Standard Edition to English, use the following command:

$ set OPENDS_JAVA_ARGS=-Duser.language=en

To make this setting permanent, right-click My Computer->Properties->Advanced. Click Environment Variables, and click New. Add the variable OPENDS_JAVA_ARGS and -Duser.language=en as its value, and click OK.

Issue 3384

Only part of the messages is localized.
To force Sun OpenDS Standard Edition to use English even if the operating system is using a non-English locale:

• On UNIX or Linux platforms:

  $ export LC_ALL=en_US.UTF-8
  

• On Microsoft Windows, see issue 3376 about setting Sun OpenDS Standard Edition to English.

Issue 3392

Replication conflicts currently exist under the following scenarios:

• Scenario: mod_del + mod_add of a multiple-valued attribute
• Scenario: double mod_add over a multi-valued attribute
• Scenario: double_del on a multiple-valued attribute
• Scenario: double mod_del on a single-valued attribute
• Scenario: double mod_rdn of the same entry
• Scenario: two opposite mod_rdn
• Scenario: mod_replace conflict with mod_rdn
  See also issues 3394, 3397, 3399, 3402, 3410.

Issue 3417

import-ldif import does not support VLV indexes.
Workaround: Import and then rebuild the index by using the rebuild-index command. For example, if you have a VLV index named, myVLVIndex . Use the following command to rebuild the index.

rebuild-index -b dc=example,dc=com -i vlv.myVLVIndex

Note - Note the vlv prefix. This step occurs after you have imported the index.

Issue 3439

Online parallel dsreplication initialization fails.
The replication mechanism does not support several total updates working in parallel on the same domain within the same replication server.

Issue 3454

Parallel dsreplication enable failure.
The dsreplication --enable does not enable multiple directory servers in parallel.
Workaround. Enable each replication server one at a time by using dsreplication --enable.

Issue 3455

Error when deleting VLV index.
When deleting a VLV index with the dsconfig command, the directory server successfully deletes the index but issues an error message that a communication problem occurred when contacting the server.

Issue 6715991

QuickSetup Welcome screen has an incorrect link to the documentation site.
Workaround: Point your web browser to the Sun OpenDS Standard Edition Documentation Center.

Issue 6720079

No uninstall utility for the Sun OpenDS Standard Edition product files.
Workaround: You must remove the Sun OpenDS SE installation directory manually.