Directory Proxy Server Upgrade

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

• Pre-Upgrade Tasks

• To Verify Current Version Information

• To Verify the Upgrade

• Rolling Back the Upgrade

Pre-Upgrade Tasks

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

Upgrading Directory Proxy Server Dependencies

All Java ES components on a computer system and in a computing environment should be upgraded to Release 5.

When upgrading Directory Proxy Server dependencies, you should do so in the order below , before you upgrade Directory Proxy Server. Upgrade of shared components is normally achieved automatically by the Java ES installer.

• Shared Components. Release 5 installer automatically installs all required shared components in the parallel path.

• Directory Server (optional). Instructions for upgrading Directory Server to Release 5 are provided in Chapter 2, Directory Server. However, Release 5 Directory Proxy Server is supported by Release 4 Directory Server.

To Verify Current Version Information

1. Start the new Directory Proxy Server instance.

   DirectoryServer-base\dps6\bin\dpadm start instancePath

2. Check for the Directory Proxy Server version.

   DirectoryServer-base\dps6\bin\dpadm --version

   The outputs that indicate the Java ES Directory Proxy Server release version are:

   Release 5

   Sun ONE Directory Proxy Server Version 6.0

   Release 4

   Sun ONE Directory Proxy Server Version 5.2_Patch_4

Upgrade Considerations

When upgrading Directory Proxy 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 Proxy Server running on a single computer and all instances correspond to the same installed Directory Proxy Server image, upgrading the Directory Proxy Server image will require you to create new Directory Proxy Server instances.

• In Release 4 deployment architectures involving Directory Proxy Server, an Administration Server was used to configure and manage Directory Proxy Server instances. In Release 5 the upgrade of Directory Proxy Server might entail deployment of the Directory Service Control Center, used to configure and manage Directory Proxy Server instances.

To Upgrade Directory Proxy Server

Before You Begin

• Directory Proxy Server must run as the same user as Directory Server and Administration Server.

• Any Java ES components using a Directory Proxy 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 all Java ES components dependent on the Directory Proxy Server instances that are to be upgraded.

   This step might depend on how Directory Proxy Server is replicated within your deployment architecture.

   For information about how to shut down a Java ES component, see its respective administration guide.

3. Install Release 5 Directory Proxy Server.

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

4. Create a Directory Proxy Server instance.

5. (Optional) Map Release 4 configuration attributes to the Release 5 Directory Proxy Server properties.

   For more information on mapping procedure, see the Directory Server Enterprise Edition 6 Migration Guide.

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

To Verify the Upgrade

1. Change to the Server-Root\bin\dps\server\bin directory.

2. Type the following command:

   ldapfwd -v

   The outputs that indicate the Java ES Directory Proxy Server release version are:

   Release 5

   Sun ONE Directory Proxy Server Version 6.0

   Release 4

   Sun ONE Directory Proxy Server Version 5.2_Patch_4

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.