Chapter 6 Directory Proxy Server

This chapter describes how to upgrade Directory Proxy Server to Java ES 5 Update 1 (Release 5U1): Sun Java System Directory Proxy Server 6.2. It covers both feature upgrades from previous Java ES release families and maintenance upgrades from Java ES 5.

The chapter provides an overview of upgrade considerations for the different upgrade paths supported by Release 5U1. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Directory Proxy Server Upgrades

Upgrading Directory Proxy Server from Java ES 5

Upgrading Directory Proxy Server from Java ES Release 4

Upgrading Directory Proxy Server from Java ES Release 3

Upgrading Directory Proxy Server from Java ES Release 2



Note	File locations in this chapter are specified with respect to directory paths referred to as serverRoot (Directory Proxy Server 5.x) and DirServer-base (Directory Proxy Server 6.x). At least part of these paths might have been specified as installation directories when Directory Proxy Server was installed. If not, the Java ES installer assigned a default value. The default values of these directory paths are shown in the following table.

Table 6-1 Directory Proxy Server Directory Paths
Path Name Variable	Solaris OS	Linux OS
serverRoot (Directory Proxy Server 5.x)	/var/opt/mps/serverroot	/var/opt/sun/directory-server
DirServer-base (Directory Proxy Server 6.x)	/opt/SUNWdsee	/opt/sun

Overview of Directory Proxy Server Upgrades

This section describes the following general aspects of Directory Proxy Server that impact upgrading to Java ES 5 Update 1 (Release 5U1):

About Release 5U1

Release 5U1 Upgrade Roadmap

Directory Proxy Server Data

Directory Proxy Server Upgrade Strategy

About Release 5U1

Release 5U1 Directory Proxy Server is a maintenance release that fixes bugs in Release 5 Directory Proxy Server. Release 5 Directory Proxy Server was a feature release, being a new product with respect to Release 4 Directory Proxy Server and all previous releases.

Release 5U1 Directory Proxy Server is still an LDAP proxy, but with new, extensible routing capabilities. Release 5U1 also enables the Virtual Directory feature, the ability to aggregate multiple data views in a single view. These data views can represent LDAP or SQL accessible data stores.

For more information, see the Directory Server Enterprise Edition 6 Release Notes.

Release 5U1 Upgrade Roadmap

Table 6-2 shows the supported Directory Proxy Server upgrade paths to Release 5U1. The table applies to both Solaris and Linux operating systems.

Table 6-2 Upgrade Paths to Java ES 5 Update 1 (Release 5U1): Directory Proxy Server 6.2
Java ES Release	Directory Proxy Server Version	General Approach	Reconfiguration Required
Release 5	Sun Java System Directory Proxy Server 6.0	Maintenance upgrade. Apply patches.	None
Release 4	Sun Java System Directory Proxy Server 5.2 2005Q4	Feature upgrade. Direct upgrade by replacing Release 4 with a fresh install and configuration of Release 5U1.	If backward compatibility desired, manually map previous configuration to new configuration properties.
Release 3	Sun Java System Directory Proxy Server 5.2 2005Q1	Feature upgrade. Direct upgrade by replacing Release 3 with a fresh install and configuration of Release 5U1.	If backward compatibility desired, manually map previous configuration to new configuration properties.
Release 2	Sun Java System Directory Proxy Server 5.2 2004Q2	Feature upgrade. Direct upgrade by replacing Release 2 with a fresh install and configuration of Release 5U1.	If backward compatibility desired, manually map previous configuration to new configuration properties.
Release 1	Sun ONE Directory Proxy Server 5.2	Feature upgrade. Direct upgrade not certified: But you can use the same approach as upgrading from Release 2.	If backward compatibility desired, manually map previous configuration to new configuration properties.
Pre-dates Java ES releases	Sun ONE Directory Proxy Server 5.2	Feature upgrade. Direct upgrade not certified: But you can use the same approach as upgrading from Release 2.	If backward compatibility desired, manually map previous configuration to new configuration properties.
Pre-dates Java ES releases	Sun ONE Directory Access Router 5.0 or 5.0 SP1	Feature upgrade. No direct upgrade: Upgrade first to Release 3. Refer to the Java Enterprise System 2005Q1 Upgrade and Migration Guide, http://docs.sun.com/doc/819-0062. Then upgrade from Release 3 to Release 5U1.	Refer to the Java Enterprise System 2005Q1 Upgrade and Migration Guide, http://docs.sun.com/doc/819-0062.

Directory Proxy Server Data

Directory Proxy Server no longer makes use of Directory Server for storing configuration data. Configuration is performed using the new Directory Service Control Center or Directory Server EE command-line utilities.

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

Table 6-3 Directory Proxy Server Data Usage
Type of Data	Location	Usage
Directory Proxy Server configuration data	Directory Proxy Server 5.2: configuration directory Directory Proxy Server 6.x: accessed through Directory Service Control Center and Directory Server EE command-line utilities.	Configuration of Directory Proxy Server
Security data	Directory Proxy Server 5.2: SSL configured through Directory Proxy Server Console. Directory Proxy Server 6.x: SSL configured through Directory Service Control Center and Directory Server EE command-line utilities.	Server certificates

Directory Proxy Server Upgrade Strategy

Your strategy for upgrading Directory Proxy Server generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.

This section is to particularize that general discussion to Directory Proxy Server by presenting issues that might influence your Directory Proxy Server upgrade plan.

Compatibility Issues

Release 5 Directory Proxy Server introduced interface changes that make Release 5U1 Directory Proxy Server incompatible with Release 4 and earlier Directory Proxy Server releases. Release 5 Directory Proxy Server was based on a completely new Java-based implementation and its configuration differs fundamentally from Release 4 Directory Proxy Server, as well as earlier releases.

It is possible, however, to configure Release 5U1 Directory Proxy Server to be backwardly compatible, that is, to behave like Release 4 Directory Proxy Server and earlier releases. This configuration requires you to manually map previous configuration attributes to Release 5U1 configuration properties. Details are in the Directory Server Enterprise Edition 6 Migration Guide, http://docs.sun.com/doc/819-0994.

However, Release 5U1 Directory Proxy Server has different default behaviors compared to Release 4 and previous versions: it does not allow LDAP controls to pass through the proxy. To reproduce the behavior of previous versions, you can unblock these controls as described in Post-Upgrade Tasks.

Dependencies

Dependencies on other Java ES components can impact the procedure for upgrading and re-configuring Directory Proxy Server software.

Shared components. Directory Proxy Server has dependencies on specific Java ES shared components (see Table 1-10). Directory Proxy Server upgrades might depend upon upgraded versions of these shared components.

Directory Server. Directory Proxy Server has a co-dependency on Directory Server for providing improved security and performance for LDAP requests. Directory Proxy Server provides front-end access to Directory Server but has no dependency on Directory Server beyond this functional relationship.

Dual Upgrade

Fresh operating system installation

In-place operating system upgrade

Fresh Operating System Installation

Back up existing Directory Proxy Server data.

See Directory Proxy Server Data for the location of essential data.

Install the new operating system.

The operating system installation can be on a new system (or a Solaris 10 zone) or it can wipe out the existing file system.

Install Release 5U1 Directory Proxy Server.

Create a Release 5U1 Directory Proxy Server instance and map configuration attributes to the Release 5U1 Directory Proxy Server properties.

See the relevant steps in the procedure for Upgrading Release 4 Directory Proxy Server.

In-place Operating System Upgrade

Back up existing Directory Proxy Server data.

See Directory Proxy Server Data for the location of essential data.

Upgrade the operating system.

The upgrade leaves the existing file system in place.

Upgrade to Release 5U1 Directory Proxy Server.

See the relevant section of this chapter, depending on upgrade path.

Upgrading Directory Proxy Server from Java ES 5

This section includes information about upgrading Directory Proxy Server from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

Release 5 Directory Proxy Server Upgrade

Multiple Instance Upgrades

Introduction

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

General Upgrade Approach. The upgrade is achieved by patching Release 5 Directory Proxy Server.

Upgrade Dependencies. Directory Proxy Server has dependencies on a number of Java ES shared components (see Table 1-10), all of which need to be upgraded when you perform a maintenance upgrade of Directory Proxy Server.

Backward Compatibility. Release 5UI Directory Proxy Server is backwardly compatible with the Release 5 version.

Upgrade Rollback. A rollback of the Release 5U1 upgrade is achieved on Solaris OS by backing out the patch upgrade, but on the Linux platform rollback is achieved by manually reinstalling previous RPM packages.

Platform Issues. The general approach for upgrading Directory Proxy Server is the same on both Solaris and Linux operating systems.

Release 5 Directory Proxy Server Upgrade

This section describes how to perform an upgrade of Directory Proxy Server from Java ES Release 5 to Release 5U1 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Upgrading Release 5 Directory Proxy Server (Solaris)

Upgrading Release 5 Directory Proxy Server (Linux)

Verifying the Upgrade

Post-Upgrade Tasks

Rolling Back the Upgrade (Solaris)

Rolling Back the Upgrade (Linux)

Pre-Upgrade Tasks

Before you upgrade Directory Proxy Server software you should perform the following tasks:

Verify Current Version Information

Upgrade Directory Proxy Server Dependencies

Back Up Directory Proxy Server Data

Obtain Required Configuration Information and Passwords

Verify Current Version Information

You can verify the current version of Directory Proxy Server using the following command:

DirServer-base/dps6/bin/dpadm -V

Table 6-4 Directory Proxy Server Version Verification Outputs
Java ES Release	Directory Proxy Server Version Number
Release 2	Sun Java(TM) System Directory Proxy Server/5.2_Patch_2
Release 3	Sun Java(TM) System Directory Proxy Server/5.2_Patch_3
Release 4	Sun Java(TM) System Directory Proxy Server/5.2_Patch_4
Release 5	Sun Java(TM) System Directory Proxy Server/6.0
Release 5U1	Sun Java(TM) System Directory Proxy Server/6.2

If the dpadm command fails on the Solaris 10 platform, modify the value of LD_LIBRARY_PATH to remove /usr/lib (or prepend /usr/lib/mps/sasl2) and then run the dpadm command again.

Upgrade Directory Proxy Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. In particular, Release 5U1 Directory Proxy Server has hard upgrade dependencies on all of the shared components on which it depends, so these must be upgraded before upgrading Directory Proxy Server.

Back Up Directory Proxy Server Data

The Directory Proxy Server upgrade to Release 5U1 does not modify Release 5 configuration data. There is no need to back up current data.

Obtain Required Configuration Information and Passwords

No special information about your currently installed version is needed. However you will have to log in as superuser to perform the upgrade.

Upgrading Release 5 Directory Proxy Server (Solaris)

This section discusses considerations that impact the upgrade procedure for Directory Proxy Server, followed by a description of the procedure itself.

Upgrade Considerations (Solaris)

The upgrade of Directory Proxy Server software to Java ES Release 5U1 takes into account the following considerations:

Any Java ES components or applications using a Directory Proxy Server instance should be shut down if performing LDAP queries during the Directory Proxy Server upgrade or if using a library that is being patched.

In a deployment architecture in which there are multiple instances of Directory Proxy Server running on a single computer (all corresponding to the same installed Directory Proxy Server image), you only have to upgrade the Directory Proxy Server image once.

In a maintenance upgrade, you do not have to migrate schema, configuration, security and user data.

The Release 5U1 Directory Proxy Server upgrade patches for Solaris OS are shown in the following table:

Table 6-5 Patches1 to Upgrade Directory Proxy Server on Solaris
Description	Patch ID: SPARC Solaris 9 & 10	Patch ID: X86 Solaris 9	Patch ID: amd64 Solaris 10
Directory Server Enterprise Edition core (includes Directory Proxy Server)	125276-05	125277-05	125278-05
Directory Proxy Server localization	125937-05	125938-05	125938-05

1Patch revision numbers are the minimum required for upgrade to Release 5U1. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Solaris)

The procedure documented below applies to Directory Proxy Server instances residing locally on the computer where the upgrade is taking place.

su -

Shut down the Release 5 Directory Proxy Server instances (including the Directory Service Control Center).

(If Directory Server is installed on the same computer it also should be shut down.)

DirServer-base/dps6/bin/dpadm stop /instancePath

Check that the console reports a clean shutdown.

Make sure you have upgraded any Java ES components upon which Directory Proxy Server has hard upgrade dependencies (see Upgrade Directory Proxy Server Dependencies).

Obtain the latest Directory Proxy Server upgrade patches, based on Table 6-5.

To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

Apply the appropriate Directory Proxy Server core and, if needed, localization patches in Table 6-5, in that order.

patchadd /workingDirectory/patch_ID

Be sure to consult the README.patch_ID file for additional patch installation instructions.

Confirm that the patch upgrades were successful:

showrev -p | grep patch_ID

The output should return the versions of patch IDs applied in Step 5.

Restart the Directory Proxy Server instances (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm start /instancePath

Upgrading Release 5 Directory Proxy Server (Linux)

This section discusses considerations that impact the upgrade procedure for Directory Proxy Server, followed by a description of the procedure itself.

Upgrade Considerations (Linux)

The upgrade of Directory Proxy Server software to Java ES Release 5U1 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 5U1 upgrade patches differ from the Solaris patches.

The Release 5U1 Directory Proxy Server upgrade patches for Linux OS are shown in the following table:

Table 6-6 Patches1 to Upgrade Directory Proxy Server on Linux
Description	Patch ID and RPM names
Directory Server Enterprise Edition core (includes Directory Proxy Server)	125309-05 sun-ldap-proxy-6.2-5.i386.rpm sun-ldap-proxy-client-6.2-5.i386.rpm sun-ldap-proxy-config-6.2-5.i386.rpm sun-ldap-proxy-man-6.2-5.i386.rpm sun-ldap-shared-6.2-5.i386.rpm
Directory Service Control Center	sun-ldap-console-agent-6.2-5.i386.rpm sun-ldap-console-cli-6.2-5.i386.rpm sun-ldap-console-gui-6.2-5.i386.rpm sun-ldap-console-gui-help-6.2-5.i386.rpm
Directory Proxy Server localization	125939-06 sun-ldap-console-gui-help-l10n-6.2-6.i386.rpm sun-ldap-console-gui-l10n-6.2-6.i386.rpm sun-ldap-proxy-client-l10n-6.2-6.i386.rpm sun-ldap-proxy-l10n-6.2-6.i386.rpm sun-ldap-shared-l10n-6.2-6.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Release 5U1. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Linux)

The procedure documented below applies to Directory Proxy Server instances residing locally on the computer where the upgrade is taking place.


Caution	An upgrade from Release 5 to Release 5U1 on Linux cannot easily be rolled back.

su -

Shut down the Release 5 Directory Proxy Server instances (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm stop /instancePath

Check that the error log (/instancePath/logs/errors) reports a clean shutdown:

Make sure you have upgraded any Java ES components upon which Directory Proxy Server has hard upgrade dependencies (see Upgrade Directory Proxy Server Dependencies).

Obtain the latest Directory Proxy Server upgrade patches, based on Table 6-6.

To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

Apply the core and, if needed, localization patch for Directory Proxy Server in Table 6-6, in that order.

cd /workingDirectory/patch_ID
./installpatch

If installpatch reports any errors, you will need to resolve the reported errors and run installpatch again.

Be sure to consult the README.patch_ID file for additional patch installation instructions.

Confirm that the patch upgrades were successful.

rpm -qa | grep sun-ldap-proxy

The new version numbers of the RPMs should be returned.

Restart the Directory Proxy Server instances that were stopped in (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm start /instancePath

Verifying the Upgrade

Check the current version of Directory Proxy Server:

DirServer-base/dps6/bin/dpadm -V

See Table 6-4 for output values.

Check the startup messages in the Directory Proxy Server error log:

instancePath/logs/errors



Note	At startup, Release 5U1 Directory Proxy Server detects circular definitions. These circular definitions are functionally benign, but can result in a large number of errors when you upgrade from a previous version which contains such circular definitions.

Post-Upgrade Tasks

Rolling Back the Upgrade (Solaris)

This section describes the Release 5U1 upgrade rollback procedure for Directory Proxy Server on the Solaris platform.

su -

Stop all running instances of Directory Proxy Server (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm stop /instancePath

Remove the patches in Table 6-5.

patchrm patch_ID

Restart the Directory Proxy Server instances that were stopped in Step 2 (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm start /instancePath

Rolling Back the Upgrade (Linux)

This section describes the Release 5U1 upgrade rollback procedure for Directory Proxy Server on the Linux platform. There is no automated rollback procedure for Linux patches, so the recommended approach is to manually overwrite the Release 5U1 RPMs with the Release 5 RPMs, as described below.

su -

Stop all running instances of Directory Proxy Server (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm stop /instancePath

Check the revision numbers of Directory Proxy Server RPMs.

rpm -qa | grep sun-ldap

The updated RPMs should be those listed in Table 6-6.

Check to see if the RPMs have been relocated from their default location.

rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

where rpmName is the unique name of the RPM (for example, the values sun-ldap-* shown in Table 6-6). The command returns a prefixValue as a path to the installed RPM.

Reinstall Release 5 RPMs from the Java ES 5 distribution.

(If you are rolling back to a post-Release 5 sustaining patch, rather than to Release 5, reinstall the RPMs from that patch.)

rpm -Uvh --force [--prefix prefixValue] *.rpm

The --force option will allow the command to overwrite later packages of the same name. The --prefix option is not required unless the RPMs have been relocated. (If only a subset of the RPMs had been relocated, use individual file names as command arguments rather than *.rpm.)

Start the Directory Proxy Server instances that were stopped in Step 2 (including the Directory Service Control Center).

DirServer-base/dps6/bin/dpadm start /instancePath

Multiple Instance Upgrades

In some deployment architectures Directory Proxy Server is deployed on multiple computer systems to provide for scalability and to improve availability. For example, you might have Directory Proxy Server components running on multiple computers with a load balancer to distribute the load.

In the case of load-balanced instances of Directory Proxy Server, you cannot perform a rolling upgrade; the load balancer needs to be shut down and re-configured to access the Release 5U1 instances. You perform the upgrade of each instance as described in Release 4 Directory Proxy Server Upgrade.

Upgrading Directory Proxy Server from Java ES Release 4

This section includes information about upgrading Directory Proxy Server from Java ES 2005Q4 (Release 4) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

Release 4 Directory Proxy Server Upgrade

Multiple Instance Upgrades

Introduction

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

General Upgrade Approach. The upgrade is achieved by performing a fresh install of Release 5U1 Directory Proxy Server and then configuring new Directory Proxy Server instances using the Directory Service Control Center or Directory Server EE command-line utilities.

Upgrade Dependencies. Directory Proxy Server has dependencies on a number of Java ES shared components (see Table 1-10), all of which are automatically upgraded to Release 5U1 by the Java ES installer when you perform an upgrade of Directory Proxy Server.

Backward Compatibility. Release 5U1 Directory Proxy Server can be configured to be backwardly compatible with its Release 4 version, as explained in Compatibility Issues.

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

Platform Issues. The general approach for upgrading Directory Proxy Server is the same on both Solaris and Linux operating systems.

Release 4 Directory Proxy Server Upgrade

This section describes how to perform an upgrade of Directory Proxy Server from Release 4 to Release 5U1 on both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Upgrading Release 4 Directory Proxy Server

Verifying the Upgrade

Post-Upgrade Tasks

Rolling Back the Upgrade

Pre-Upgrade Tasks

Before you upgrade Directory Proxy Server software you should perform the following tasks:

Verify Current Version Information

Upgrade Directory Proxy Server Dependencies

Obtain Required Configuration Information and Passwords

Verify Current Version Information

You can verify the current version of Directory Proxy Server using the following commands:

Upgrade Directory Proxy Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Directory Proxy Server has hard upgrade dependencies on only a few shared components.

When upgrading Directory Proxy Server dependencies, you should do so in the order below (skipping any that might already have been upgraded), before you upgrade Directory Proxy Server. Upgrade of shared components is normally achieved automatically by the Java ES installer.

Shared Components. Instructions for synchronizing Java ES shared components to Release 5U1 are provided in Upgrading Java ES Shared Components. However, all shared components required by Directory Proxy Server are upgraded automatically by the Java ES installer when you perform an upgrade of Directory Proxy Server to Release 5U1.

Directory Server (soft upgrade dependency) Instructions for upgrading Directory Server to Release 5U1 are provided in Chapter 5, "Directory Server". However, Release 5U1 Directory Proxy Server is supported by Release 4 Directory Server.

Obtain Required Configuration Information and Passwords

Configuration information is preserved through the upgrade process and can be used to map Release 4 configuration attributes to Release 5U1 configuration properties. See Compatibility Issues.

Upgrading Release 4 Directory Proxy Server

This section discusses considerations that impact the upgrade procedure for Directory Proxy Server followed by a description of the procedure itself.

Upgrade Considerations

The upgrade of Directory Proxy Server software to Release 5U1 takes into account the following considerations:

Any Java ES components using a Directory Proxy Server instance (such as Access Manager, Communications Express, Messaging Server, Portal Server, and so forth) should be shut down and re-configured to access the corresponding new Release 5U1 instance.

In a deployment architecture in which there are multiple instances of Directory Proxy Server running on a single computer (all corresponding 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 5U1 the upgrade of Directory Proxy Server might entail deployment of the Directory Service Control Center, used to configure and manage Directory Proxy Server instances.

Upgrade Procedure

The procedure documented below applies to Directory Proxy Server instances residing locally on the computer where the upgrade is taking place.

su -

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.

Perform a fresh install of Release 5U1 Directory Proxy Server.

Perform the following steps:

Launch the Java ES installer.

cd Java ES Release 5U1 distribution/os_arch
./installer

where os_arch matches your platform, such as Solaris_sparc. (Use the installer -nodisplay option for the command line interface.)

After the Welcome and License Agreement pages are displayed, you will be presented with a component selection page. (When installed components are detected that can be directly upgraded by the Java ES installer, they are shown with a status of "upgradable.")

Select the Directory Proxy Server subcomponent of Directory Server Enterprise Edition.

You will also need to install the administrative subcomponents (Directory Service Control Panel or command line utilities) you wish to use.

Specify an installation path different from that of any existing Release 4 Directory Proxy Server.

Choose to Configure Now or Configure Later.

It does not matter whether you choose to configure now or to configure later because there is really no configuration required for Directory Proxy Server. However, if you choose to configure now, you are asked if you want to create a new instance. (Once the component is installed, you can create as many Directory Proxy Server instances as you wish.)

If needed, select the option to install localized packages.

Confirm your installation choices.

Directory Proxy Server packages will be installed and an installation summary displayed.

Exit the Java ES installer.

If you have not created a new instance, continue to Step 5, otherwise continue with Step 6.

Apply the latest Directory Proxy Server maintenance patches, if any.

Check if there have been any Directory Proxy Server point fixes subsequent to Release 5U1.

Periodically obtain the latest patches as described in Accessing Java ES Patches and compare them to the Release 5U1 patch revision numbers shown in Table 6-5 (Solaris) or Table 6-6 (Linux).

If you are using Sun Connection on the Solaris platform, you are automatically notified of new patches for Java ES components installed on your computer.

Apply the appropriate Directory Proxy Server core and, if needed, localization patches in that order.

On Solaris:
patchadd /workingDirectory/patch_ID

If you are using the accumulated patch cluster on the Solaris platform, the install_cluster script will apply any Java ES patches needed on your computer.

On Linux:
cd /workingDirectory/patch_ID
./installpatch

Be sure to consult the README.patch_ID file for additional patch installation instructions.

Confirm that the patch upgrades were successful:

On Solaris:
showrev -p | grep patch_ID

On Linux:
rpm -qa | grep sun-ldap-proxy

The output should return the appropriate patch IDs or version numbers.

Create a Directory Proxy Server instance.

DirServer-base/dps6/bin/dpadm create instancePath

where instancePath is the full path to the Directory Proxy Server instance.

For information on creating a Directory Proxy Server instance, see the Directory Server Enterprise Edition 6 Administration Guide, http://docs.sun.com/doc/819-0995.

If desired, map Release 4 configuration attributes to the Release 5U1 Directory Proxy Server properties.

For details of the mapping procedure, see the Directory Server Enterprise Edition 6 Migration Guide, http://docs.sun.com/doc/819-0994.

Verifying the Upgrade

Post-Upgrade Tasks

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

In addition, to reproduce the default behavior of previous versions, LDAP controls must be explicitly allowed to pass through the proxy. You can enabled these controls by setting the allowed-ldap-controls property as follows:

./dpconf set-server-prop
allowed-ldap-controls:auth-request
allowed-ldap-controls:chaining-loop-detection
allowed-ldap-controls:manage-dsa
allowed-ldap-controls:persistent-search
allowed-ldap-controls:proxy-auth-v1
allowed-ldap-controls:proxy-auth-v2
allowed-ldap-controls:real-attributes-only
allowed-ldap-controls:server-side-sorting

Rolling Back the Upgrade

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

Multiple Instance Upgrades

Upgrading Directory Proxy Server from Java ES Release 3

The procedure for upgrading Java ES 2005Q1 (Release 3) Directory Proxy Server to Release 5U1 is the same as that for upgrading Release 4 Directory Proxy Server to Release 5U1.

Upgrading Directory Proxy Server from Java ES Release 2

Java ES certifies indirect upgrade from Java ES 2004Q2 (Release 2) Directory Proxy Server by first upgrading to Release 5 Directory Proxy Server (as documented in the Java Enterprise System 5 Update 1 Upgrade Guide for UNIX, http://docs.sun.com/doc/819-6553:) and then upgrading from Release 5 Directory Proxy Server to Release 5U1Directory Proxy Server (as documented in Upgrading Directory Proxy Server from Java ES 5).

However, direct upgrade is also supported. The procedure for directly upgrading Release 2 Directory Proxy Server to Release 5U1 is the same as that for upgrading Release 4 Directory Proxy Server to Release 5U1, with the exception that the pre-upgrade tasks should include the upgrading to Release 5U1 of all shared components upon which Directory Proxy Server depends (see Table 1-10).

Previous Contents Index Next
Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX


Note	If you are upgrading from Release 2 Directory Proxy Server on the Linux platform, then you will have to perform a dual upgrade, in which both Directory Proxy Server and the operating system are upgraded (Release 5U1 Directory Proxy Server is not supported on RHEL 2.1). See Dual Upgrade for more information.