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

• To Verify Current Version Information

• To Verify the Upgrade

• Post-Upgrade Tasks

• Rolling Back the Upgrade

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

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

2. 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.

1. Log in as administrator.

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

3. 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.

   ---

4. 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

5. 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.

6. 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.

7. 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

1. Log in as administrator.

2. Start the new Directory Server instance.

   DirectoryServer-base\ds6\bin\dsadm -V

3. 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.