Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows

Overview of Directory Server Upgrade

This following sections describe general aspects of Directory Server that affect upgrading to Java ES 5:

About Java ES 5 Directory Server

Java ES 5 versions of Directory Server represents a major release, with a variety of new features and improvements. For more information, see the Sun Java System Directory Server Enterprise Edition 6.0 Release Notes.

Java ES 5 Directory Server Upgrade Roadmap

Because the Java ES Release 5 version of Directory Server represents a major release, you install the new Directory Server version and migrate user and configuration data from the previous Directory Server version. For migrations instructions to the new version, see the Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide.

The following table shows the supported Directory Server upgrade path to Java ES 5:

Table 2–1 Upgrade Paths to Java ES 5 Directory Server


Java ES Release	Directory Server Release	General Approach	Reconfiguration Required as Part of Upgrade
Release 4	Sun Java System Directory Server 5.2 2005Q4 Sun Java System Administration Server 5.2 2005Q4	Direct upgrade: Fresh install and migration of all data. Administration Server functionality replaced by Directory Service Control Center and Directory Server EE command-line utilities	Configuration data migrated from previous version to newly installed Directory Server

Directory Server Data

Directory Server 5.x versions made use of Directory Server itself for storing configuration data. The data was stored in a specific tree structure within the directory. The Directory Server instance that hosted the configuration was referred to as the configuration directory. The configuration directory could reside on the same computer as other Directory Server instances. However, in most deployment architectures, the configuration directory was remote from the other components that use it to store configuration information.

Directory Server 6.0 no longer stores configuration data in a configuration directory. Configuration is performed using the Directory Service Control Center or the Directory Server EE command-line utilities. The configuration should be accessed through this interface.

The following table shows the type of data that could be impacted by an upgrade of Directory Server software.

Table 2–2 Directory Server Data Usage


Type of Data	Location	Usage
Directory Server configuration data	Directory Server 5.x: configuration directory Directory Server 6.0: accessed through Directory Service Control Center and Directory Server EE command-line utilities	Configuration of Directory Server
Directory Server schema		Define structure and semantics of data in the directory
Security data	Directory Server 5.x: SSL configured through Directory Server Console. Directory Server 6.0: SSL configured through Directory Service Control Center and Directory Server EE command-line utilities	Server certificates
User data	Directory Server	Server certificates

Directory Server Compatibility Issues

Release 5 Directory Server does not introduce any interface changes and is therefore backwardly compatible with earlier versions. However, Directory Server supports all components supported by Release 4 Directory Server and earlier versions.

Release 5 introduces changes to private administrative interfaces that make Release 5 incompatible with earlier releases of Directory Server. Details can be found in the Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide. In particular, the Administration Server, used to configure earlier Directory Server instances, has been replaced by the Directory Service Control Center and Directory Server EE command-line utilities. The o=NetscapeRoot directory suffix for storing Directory Server configuration information has been eliminated.

Directory Server Dependencies

Dependencies on other Java ES components can affect the procedure for upgrading Directory Server software. Directory Server has dependencies on specific Java ES shared components, as listed in Table 1–7.