Directory Server Changes

Starting with Directory Server Enterprise Edition Bundle Patch 6.3.1.1.1, the use of Cacao and the use of Java Enterprise Monitoring Framework (JESMF) are deprecated and will be replaced in a future release. Also, commands dsccsetup initialize and dsccsetup dismantle should be considered deprecated and will be removed in a future release.

The legacy command-line tools for managing Directory Server instances are deprecated.

The following tools might be removed from a future release.

• bak2db

• db2bak

• db2ldif

• ldif2db

• restart-slapd

• start-slapd

• stop-slapd

New command line tools, dsadm and dsconf, and other commands replace the functionality provided by the tools listed. See “Command Line Changes” in the Sun Java System Directory Server Enterprise Edition 6.3 Migration Guidefor details.

For a detailed discussion of administration related Directory Server changes, see “Chapter 5, Architectural Changes in Directory Server” in the Sun Java System Directory Server Enterprise Edition 6.3 Migration Guide.

Before migrating a replicated server topology, see “Chapter 4, Migrating a Replicated Topology” in the Sun Java System Directory Server Enterprise Edition 6.3 Migration Guide.

When you create a Directory Server instance, password policy is configured initially backwards-compatible. After upgrading, you change the compatibility mode to enable richer password policy configuration. Directory Server manages the conversion. In a future release, the backwards-compatible password policy configuration might be removed.

Also, when you create a Directory Server instance, support for the modify DN operation is disabled. After upgrade all server instances in your replication topology, the modify DN operation can be replicated properly. At that point, you can enable support for the modify DN operation on each server instances. Use the dsconf set-server-prop moddn-enabled:on command for this purpose.

Directory Server chaining is deprecated and might be removed in a future release. Chaining is not configurable through Directory Service Control Center, nor is chaining configurable through the new command line tools. Most deployments enabled by chaining are now enabled using features of Directory Proxy Server. For example, data distribution, global account lockout across an entire replication topology, and merging directory information trees can be done with Directory Proxy Server. For legacy applications that continue to rely on chaining, you can configure the chained suffix plug-in with the ldapmodify command to set attributes for chaining. The attributes are listed in Sun Java System Directory Server Enterprise Edition 6.3 Man Page Reference.

Chapter 2, Changes to the Plug-In API Since Directory Server 5.2, in Sun Java System Directory Server Enterprise Edition 6.3 Developer’s Guide and Chapter 3, Changes to the Plug-In API From Directory Server 4 to Directory Server 5.2, in Sun Java System Directory Server Enterprise Edition 6.3 Developer’s Guide detail plug-in API changes. Interfaces identified there as deprecated might be removed in a future release.