This chapter covers features that have been deprecated or removed from Directory Server Enterprise Edition component products. This chapter also covers features that are susceptible to removal, and functionality that is susceptible to deprecation for Directory Server Enterprise Edition component products.
This chapter includes the following sections:
Classifications of interface stability are provided per manual page entry in Sun Java System Directory Server Enterprise Edition 6.2 Man Page Reference.
In a future release of Directory Server Enterprise Edition, support for Windows 2000, Red Hat Advanced Server 3.0, and J2SE platform 1.4 may be removed. Support for 32–bit versions of the software might be discontinued for some platforms. To be prepared, start planning the transition to newer versions of Windows, Red Hat, and the Java SE platform and to 64–bit versions of the software.
Directory Server Enterprise Edition 6.2 does not support HP-UX. But the future version of the product is planned to support HP-UX.
Directory Server Enterprise Edition 6.2 also supports SuSE Linux Enterprise Server 9 Service Pack 3 but only for zip distribution.
System virtualization is a technology that enables multiple operating system (OS) instances to execute independently on shared hardware. Functionally, software deployed to an OS hosted in a virtualized environment is generally unaware that the underlying platform has been virtualized. Sun performs testing of its Sun Java System products on select system virtualization and OS combinations to help validate that the Sun Java System products continue to function on properly sized and configured virtualized environments as they do on non-virtualized systems. For information about Sun support for Sun Java System products in virtualized environments, see http://download.oracle.com/820-4651.
Administration Server and the Java Swing-based Console used for remote graphical administration of Identity Synchronization for Windows may be replaced in a future release. Directory Service Control Center has been implemented to allow full browser-based service management, with easier configuration for access through a firewall.
Directory Proxy Server and Directory Server already use Directory Service Control Center. Directory Proxy Server and Directory Server no longer use the serverroot architecture, but instead the new administration framework.
As a result, the following commands may not be included in a future release, even for Identity Synchronization for Windows:
In addition, everything in o=NetscapeRoot, may change. In particular, o=NetscapeRoot might no longer be present. The serverroot architecture may be replaced by the new administration framework.
Furthermore, Directory Server chaining cannot be configured through Directory Service Control Center.
The legacy command-line tools for managing Directory Server instances are deprecated.
The following tools have already been removed.
The following tools might be removed from a future release.
The new command line tools, dsadm and dsconf, and other commands replace the functionality provided by the tools listed. See Command Line Changes in Sun Java System Directory Server Enterprise Edition 6.2 Migration Guide for details.
For a detailed discussion of administration related Directory Server changes, see Chapter 5, Architectural Changes in Directory Server, in Sun Java System Directory Server Enterprise Edition 6.2 Migration Guide.
Before migrating a replicated server topology, review Chapter 4, Migrating a Replicated Topology, in Sun Java System Directory Server Enterprise Edition 6.2 Migration Guide. Support for legacy replication with Directory Server 4 has been removed from this release. Sun Microsystems ended support for Directory Server 4 in January 2004.
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 dse.ldif(4).
Chapter 2, Changes to the Plug-In API Since Directory Server 5.2, in Sun Java System Directory Server Enterprise Edition 6.2 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.2 Developer’s Guide detail plug-in API changes. Interfaces identified there as deprecated might be removed in a future release.
To access Directory Proxy Server 6.0 and 6.1 instances using the Directory Proxy Server 6.2 commands, no migration is required. But all the Directory Proxy Server 5.x instances need to be migrated before using with the Directory Proxy Server 6.2 commands. See Chapter 6, Migrating Directory Proxy Server, in Sun Java System Directory Server Enterprise Edition 6.2 Migration Guide for details.
Future releases of Identity Synchronization for Windows might discontinue support for all versions and service packs of Microsoft Windows NT. Microsoft ended support for Windows NT in June 2004.
Before upgrading Identity Synchronization for Windows, read Chapter 7, Migrating Identity Synchronization for Windows, in Sun Java System Directory Server Enterprise Edition 6.2 Migration Guide.
About Directory Server Resource Kit explains what is provided in this release of Directory Server Resource Kit.
The LDAP utility manual pages on Sun Solaris systems do not document the version of the LDAP utilities ldapsearch, ldapmodify, ldapdelete, and ldapadd delivered with Directory Server Enterprise Edition. The commands might no longer be delivered separately on Solaris systems, but instead integrated with the commands provided by the operating system in a future version. See Sun Java System Directory Server Enterprise Edition 6.2 Man Page Reference for the manual pages for the LDAP client tools.