Sun Java Enterprise System 5 Upgrade Guide for Microsoft Windows

Chapter 2 Directory Server

This chapter describes how to upgrade Directory Server to Java ES 5: Sun Java System Directory Server 6.0.

The chapter provides an overview of upgrade issues and procedures for the different upgrade paths supported by Release 5. This chapter covers the following topics:

Note –

File locations in this chapter are specified with respect to a directory path referred to as Server-Root (Directory Server 5.x) and DirectoryServer-base (Directory Server 6.0). At least part of this path might have been specified as an installation directory when Directory Server was initially installed. If not, the Java ES installer assigned a default value.

The default value of Server-Root is Install-dir\Server_Root and DirectoryServer-base is C:\Program Files\Sun\JavaES5\DSEE.

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.

Upgrading Directory Server from Java ES Release 4

This section includes information about upgrading Directory Server from Release4 to Release 5. This section covers the following topics:

Introduction to Upgrading Directory Server

When upgrading Release 4 Directory Server to Release 5, consider the following aspects of the upgrade process:

General Upgrade Approach. The upgrade is achieved by performing a fresh install of Release 5 Directory Server and then using migration tools to recreate the previous Directory Server instances in new, distinct Release 5 Directory Server instances.
Upgrade Dependencies. Directory Server has dependencies on a number of Java ES shared components, as listed in Table 1–7. Shared components are automatically upgraded to Release 5 by the Java ES installer when you perform an upgrade of Directory Server.
Backward Compatibility. Release 5 Directory Server is not backwardly compatible with the Release 4 version. However, you can use the migration tools to migrate the o=NescapeRoot suffix if you continue to maintain a set of Directory Server instances relying on the Directory Server 5.x administration framework.
Upgrade Rollback. You can do a rollback of the Release 5 upgrade is achieved by reverting to the previous version, which is left intact by the upgrade.

Directory Server Upgrade

This section describes how to perform an upgrade of Directory Server from Release 4 to Release 5. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Directory Server, perform the tasks described below.

Upgrade Directory Server Dependencies

All Java ES components on a computer system and in a computing environment should be upgraded to Release 5. However, all shared components required by Directory Server are upgraded automatically when you perform an upgrade of Directory Server to Release 5.

Create Directory Server Image (Optional)

In cases where Release 5 Directory Server is being installed on a computer different from where the Release 4 version resides, an image of the Release 4 version should be created on the computer where Release 5 Directory Server is being installed. The image is needed to automate data migration (using the dsmig.bat) to the new Release 5 Directory Server instances.

Release 4 image includes all schema files, configuration files, security files, and database files, in an identical layout to the original Directory Server 5.x file structure. The image is needed to perform data migration to the new Release 5 Directory Server instances.

To Verify Current Version Information

Go to Server-Root\bin\slapd-hostname\server

Type the following command:

ns-slapd -v

The message that indicate the Java ES release version are:

Release 5

Sun Java System Directory Server 6.0

Release 4

Sun Java System Directory Server 5.2_Patch_4

Upgrade Considerations

When upgrading Directory Server software to Java ES Release 5 you should take into account the following considerations:

In a deployment architecture in which there are multiple instances of Directory Server running on a single computer and all instances correspond to the same installed Directory Server image, upgrading the Directory Server image will upgrade all the instances. In such architectures, there is only one Administration Server instance per installed Directory Server image.
In many Release 4 deployment architectures the configuration directory is a separate Directory Server instance. These instances do not need to be upgraded because the configuration directory has been deprecated in Release 5. On the other hand, the upgrade might entail the deployment of the Release 5 Directory Server administrative console (the Directory Service Control Center) to a separate computer from which you remotely manage Directory Server instances.

To Upgrade Directory Server to Java ES Release 5

Before You Begin

Obtain the Directory Server administrator user ID and password for your currently installed version. Other configuration information is preserved through the upgrade process.
Any Java ES components using a Directory Server instance should be shut down and re-configured to access the corresponding new Release 5 instance.

Shut down the Release 4 Directory Server (5.2) instances.

For remote install of Release 5, create a Release 4 image and transfer it to the remote computer, see Create Directory Server Image (Optional).

Note –
If the old and the new versions of the Directory Server have been installed on two different machines, an image of the old Directory Server must be created on the same machine where the new Directory Server is installed.

Make sure you have upgraded any Java ES components upon which Directory Server and Administration Server have hard upgrade dependencies.

For more information, see Upgrade Directory Server Dependencies

Install Release 5 Directory Server.

For Java ES 5 Directory Server installation instructions, see the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

Create a Directory Server instance.

For information about creating a Directory Server instance, see the Sun Java System Directory Server Enterprise Edition 6.0 Administration Guide.

Migrate Release 4 data to the Release 5 Directory Server instance.

For more information about the migration process, see the Sun Java System Directory Server Enterprise Edition 6.0 Migration Guide.

To Verify the Upgrade

Start the new Directory Server instance.

DirectoryServer-base\ds6\bin\dsadm -V

Check the startup messages in the instance-path\logs\errors Directory Server error log.

The message that indicate the Java ES release version are:

Release 5

Sun Java System Directory Server 6.0

Release 4

Sun Java System Directory Server 5.2_Patch_4

Post-Upgrade Tasks

All Java ES components dependent on Directory Server need to be re-configured to point to the new Directory Server instances.

Rolling Back the Upgrade

A rollback of the Release 5 upgrade is achieved by reverting to the previous version, which is left intact by the upgrade to Release 5.