Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX 

Chapter 5
Directory Server

This chapter describes how to upgrade Directory Server to Java ES 5 Update 1 (Release 5U1): Sun Java System Directory 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 Server Upgrades

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

About Release 5U1

Release 5U1 Directory Server is a maintenance release that fixes bugs in Release 5 Directory Server. Release 5 Directory Server was a feature release, with a variety of new features and improvements. See the Directory Server Enterprise Edition 6 Release Notes, http://docs.sun.com/doc/819-0991 for details.

Java ES Release 5U1 Upgrade Roadmap

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

Table 5-2 Upgrade Paths to Java ES 5 Update 1 (Release 5U1): Directory Server 6.2

Java ES Release

Directory Server Version

General Approach

Reconfiguration Required

Release 5

Sun Java System Directory Server 6.0

Maintenance upgrade. Apply patches.

None

Release 4

Sun Java System Directory Server 5.2 2005Q4

Sun Java System Administration Server 5.2 2005Q4

Feature upgrade. Direct upgrade through 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

Release 3

Sun Java System Directory Server 5 2005Q1

Sun Java System Administration Server 5 2005Q1

Feature upgrade. Direct upgrade through 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

Release 2

Sun Java System Directory Server 5.2 2004Q2

Sun Java System Administration Server 5.2 2004Q2

Feature upgrade. Direct upgrade is supported through fresh install and migration of all data. Indirect upgrade is also supported by upgrading first to Release 5 and then from Release 5 to Release 5U1.

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

Release 1

Sun ONE Directory Server 5.2

Sun ONE Administration Server 5.2

Feature upgrade. Direct upgrade not certified, but you can use the same approach as upgrading from Release 2.

Configuration data migrated from previous version to newly installed Directory Server

Pre-dates Java ES releases

Sun ONE Directory Server 5.2

Sun ONE Administration Server 5.2

Feature upgrade. Direct upgrade not certified, but you can use the same approach as upgrading from Release 2.

Configuration data migrated from previous version to newly installed Directory Server

Sun ONE Directory Server 5.1

Sun ONE Administration Server 5.1

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 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 hosting 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.x 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), and should be accessed through this interface. Directory Service Control Center stores configuration data in its own local Directory Server instance.

The following table shows the type of data that can be impacted by an upgrade of Directory Server software to Release 5U1.

Table 5-3 Directory Server Data Usage

Type of Data

Location

Usage

Directory Server configuration data

Directory Server 5.1 and 5.2: configuration directory

Directory Server 6.x: accessed through Directory Service Control Center and Directory Server EE command-line utilities

Configuration of Directory Server instances

Directory Server schema

Directory Server 5.1 and 5.2:
serverRoot/slapd-instanceName/config/schema/

Directory Server 6.x:
instancePath/config/schema/

Define structure and semantics of data in the directory

Security data

Directory Server 5.1 and 5.2: SSL configured through Directory Server Console.

Directory Server 6.x: SSL configured through Directory Service Control Center and Directory Server EE command-line utilities.

Server certificates.

User data

Directory Server

Support applications with user-specific configuration data and user profiles

Directory Server Upgrade Strategy

Your strategy for upgrading Directory 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 Server by presenting issues that might influence your Directory Server upgrade plan.

Compatibility Issues

Release 5U1 Directory Server does not introduce new public interfaces and is therefore backwardly compatible with earlier versions; it supports all components using Release 4 Directory Server and earlier versions.

However, Release 5 Directory Server introduced changes to private administrative interfaces. The Release 5 interfaces are incompatible with earlier releases of Directory Server. 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, and the o=NetscapeRoot directory suffix for storing Directory Server configuration information has been eliminated. Details can be found in the Directory Server Enterprise Edition 6 Migration Guide, http://docs.sun.com/doc/819-0994.

Dependencies

Dependencies on other Java ES components can, in general, impact the procedure for upgrading Directory Server software.

Directory Server has dependencies on the following Java ES components:

Dual Upgrade

Dual upgrades, in which both Directory Server and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) can be performed in either of two ways:

Fresh Operating System Installation
  1. Back up the existing Directory Server data.
  2. See Create Directory Server Image (Optional) regarding Directory Server 5.x information.

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

  5. Restore the Directory Server data that was backed up in Step 1.
  6. Install Release 5U1 Directory Server.
  7. Create a Release 5U1 Directory Server instance and migrate directory data to the new instance.
  8. See the relevant steps in the procedure for Upgrading Release 4 Directory Server.

In-place Operating System Upgrade
  1. Back up the existing Directory Server data.
  2. See Create Directory Server Image (Optional) regarding Directory Server 5.x information.

  3. Upgrade the operating system.
  4. The upgrade leaves the existing file system in place.

  5. Upgrade to Release 5U1 Directory Server.
  6. See the relevant section of this chapter, depending on upgrade path.


Upgrading Directory Server from Java ES 5

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

Introduction

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

Release 5 Directory Server Upgrade

This section describes how to perform an upgrade of Directory 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

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

Verify Current Version Information

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

If the dsadm 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 dsadm command again.

Upgrade Directory 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 Server has hard upgrade dependencies on all the shared components upon which it depends, so these must be upgraded before upgrading Directory Server.

Back Up Directory Server Data

The Directory 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 Server (Solaris)

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

Upgrade Considerations (Solaris)

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

Upgrade Procedure (Solaris)

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

  1. Log in as root or become superuser.
  2. su -

  3. Shut down the Release 5 Directory Server instances (including the Directory Service Control Center).
  4. (If Directory Proxy Server is installed on the same computer it also should be shut down.)

    DirServer-base/ds6/bin/dsadm stop /instancePath

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

    [23/Jan/2006:15:56:47 +0100] - All database threads now stopped

    [23/Jan/2006:15:56:50 +0100] - slapd stopped.

  5. Make sure you have upgraded any Java ES components upon which Directory Server has hard upgrade dependencies (see Upgrade Directory Server Dependencies).
  6. Obtain the latest Directory Server upgrade patches, based on Table 5-5.
  7. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  8. Apply the appropriate Directory Server localization, if needed, and core patches in Table 5-5, in that order.
  9. patchadd /workingDirectory/patch_ID

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

  10. Confirm that the patch upgrades were successful:
  11. showrev -p | grep patch_ID

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

  12. Restart the Directory Server instances (including the Directory Service Control Center).
  13. DirServer-base/ds6/bin/dsadm start /instancePath

Upgrading Release 5 Directory Server (Linux)

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

Upgrade Considerations (Linux)

The upgrade of Directory 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 Server upgrade patches for Linux OS are shown in the following table:

Table 5-6 Patches1 to Upgrade Directory Server on Linux 

Description

Patch ID and RPM names

Directory Server Enterprise Edition core (includes Directory Server)

125309-05

  • sun-ldap-directory-6.2-5.i386.rpm
  • sun-ldap-directory-client-6.2-5.i386.rpm
  • sun-ldap-directory-config-6.2-5.i386.rpm
  • sun-ldap-directory-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 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-directory-client-l10n-6.2-6.i386.rpm
  • sun-ldap-directory-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 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.


  1. Log in as root or become superuser.
  2. su -

  3. Shut down the Release 5 Directory Server instances (including the Directory Service Control Center).
  4. DirServer-base/ds6/bin/dsadm stop /instancePath

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

    [11/Jul/2007:16:43:01 +0200] - All database threads now stopped

    [11/Jul/2007:16:43:01 +0200] - slapd stopped.

  5. Make sure you have upgraded any Java ES components upon which Directory Server has hard upgrade dependencies (see Upgrade Directory Server Dependencies).
  6. Obtain the latest Directory Server upgrade patches, based on Table 5-6.
  7. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  8. Apply the core and, if needed, localization patch for Directory Server in Table 5-6, in that order.
  9. 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.

  10. Confirm that the patch upgrades were successful.
  11. rpm -qa | grep sun-ldap-directory

    The new version numbers of the RPMs should be returned.

  12. Restart the Directory Server instances that were stopped in Step 2 (including the Directory Service Control Center).
  13. DirServer-base/ds6/bin/dsadm start /instancePath

Verifying the Upgrade

You can verify successful upgrade of Directory Server as follows.

  1. Check the current version of Directory Server:
  2. DirServer-base/ds6/bin/dsadm -V

    See Table 5-4 for output values.

  3. Check the startup messages in the Directory Server error log:
  4. instancePath/logs/errors


    Note

    At startup, Release 5U1 Directory Server detects circular definitions in the Directory Server group entries. 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

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Considerations (Linux).

Rolling Back the Upgrade (Solaris)

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

  1. Log in as root or become superuser.
  2. su -

  3. Stop all running instances of Directory Server (including the Directory Service Control Center).
  4. DirServer-base/ds6/bin/dsadm stop /instancePath

  5. Remove the patches in Table 5-5.
  6. patchrm patch_ID

  7. Restart the Directory Server instances that were stopped in Step 2 (including the Directory Service Control Center).
  8. DirServer-base/ds6/bin/dsadm start /instancePath

Rolling Back the Upgrade (Linux)

This section describes the Release 5U1 upgrade rollback procedure for Directory 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.

  1. Log in as root or become superuser.
  2. su -

  3. Stop all running instances of Directory Server (including the Directory Service Control Center).
  4. DirServer-base/ds6/bin/dsadm stop /instancePath

  5. Check the revision numbers of Directory Server RPMs.
  6. rpm -qa | grep sun-ldap

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

  7. Check to see if the RPMs have been relocated from their default location.
  8. rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

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

  9. Reinstall Release 5 RPMs from the Java ES 5 distribution.
  10. (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.)

  11. Start the Directory Server instances that were stopped in Step 2 (including the Directory Service Control Center).
  12. DirServer-base/ds6/bin/dsadm start /instancePath

Multiple Instance Upgrades

The procedures in Release 5 Directory Server Upgrade do not explicitly deal with deployment architectures in which Directory Server is replicated for availability or scalability. These architectures might include Directory Server replication or the deployment of Directory Server as a data service in a Sun Cluster environment.

Rolling Upgrades of Directory Server Replicates

Multiple instances of Directory Server on different computer systems, such as used in multi-master replication deployment architectures, can be sequentially upgraded one instance at a time. After first synchronizing all Directory Server masters, you upgrade each instance on its respective host computer while the other instances are left running. This rolling upgrade allows the directory service to remain online while the individual Directory Server instances that provide the service are being upgraded.

Upgrading Directory Server as a Data Service

Information regarding upgrade and roll back of Directory Server as a data service in a Sun Cluster environment is currently under development.


Upgrading Directory Server from Java ES Release 4

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

Introduction

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

Release 4 Directory Server Upgrade

This section describes how to perform an upgrade of Directory Server from Java ES 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

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

Verify Current Version Information

You can verify the current version of Directory Server by restarting the Directory Server daemon using the -v option:

If the ns-slapd 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 ns-slapd command again.

Upgrade Directory 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. However, all shared components required by Directory Server are upgraded automatically when you perform an upgrade of Directory Server to Release 5U1.

Obtain Required Configuration Information and Passwords

You should know the Directory Server administrator user ID and password for your currently installed version. Other configuration information is preserved through the upgrade process.

Create Directory Server Image (Optional)

In cases where Release 5U1 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 5U1 Directory Server is being installed. The image is needed to automate data migration (using the dsmig command) to the new Release 5U1 Directory Server instances.

The 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 serverRoot file structure. The image is needed to perform data migration to the new Release 5U1 Directory Server instances.

Upgrading Release 4 Directory Server

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

Upgrade Considerations

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

Upgrade Procedure

The procedure documented below applies to Directory Server instances residing locally on the computer where the upgrade is taking place, or in the case where instances are moving to another computer, all instances that will run on the target computer.

  1. Log in as root or become superuser.
  2. su -

  3. Shut down the Release 4 Directory Server (5.2) instances.
  4. serverRoot/slapd-instanceName/stop-slapd

    Check that the error log (serverRoot/slapd-hostName/logs/errors) reports a clean shutdown:

    [23/Jan/2006:15:56:47 +0100] - All database threads now stopped

    [23/Jan/2006:15:56:50 +0100] - slapd stopped.

  5. Ensure that the host computer for Release 5U1 Directory Server has sufficient disk space.
  6. The basic calculation is as follows:
    2 * (space for existing server) + (space for LDIF files)

    There is unfortunately no tool allowing to anticipate the size of an LDIF file created from an exported database. The size will depend upon the number of data entries, their internal representation, the number of indexes, and so forth.

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

  9. Make sure you have upgraded any Java ES components upon which Directory Server has hard upgrade dependencies (see Upgrade Directory Server Dependencies).
  10. Perform a fresh install of Release 5U1 Directory Server.
  11. Perform the following steps:

    1. Launch the Java ES installer.
    2. 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.")

    3. Select the Directory Server subcomponent of Directory Server Enterprise Edition.
    4. You will also need to install the administrative subcomponents (Directory Service Control Panel or command line utilities) you wish to use.

    5. Specify an installation path different from that of any existing Release 4 Directory Server.
    6. Choose to Configure Now or Configure Later.
    7. It does not matter whether you choose to Configure Now or to Configure Later because there is really no configuration required for Directory Server. However, if you choose to Configure Now, do not opt to create a new instance.

    8. Confirm your installation choices.
    9. Directory Server packages will be upgraded and an upgrade summary displayed.

    10. Exit the Java ES installer.
  12. Apply the latest Directory Server maintenance patches, if any.
    1. Check if there have been any Directory Server point fixes subsequent to Release 5U1.
    2. 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 5-5 (Solaris) or Table 5-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.

    3. Apply the appropriate Directory Server core and, if needed, localization patches in that order.
    4. 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.

    5. Confirm that the patch upgrades were successful:
    6. On Solaris:
      showrev -p | grep patch_ID

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

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

  13. Create a Directory Server instance.
  14. DirServer-base/ds6/bin/dsadm create instancePath

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

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

    If you fail to create a new instance, a new instance will automatically be created for you when you migrate data with the dsmig command (Step 9).

  1. Migrate Release 4 data to the Release 5U1 Directory Server instance.
  2. Use the DirServer-base/ds6/bin/dsmig commands.

    The dsmig commands adapt the Release 4 data to the Release 5U1 format and write it to the appropriate locations. For example, a typical migration on a single computer with one Directory Server instance might look like this:

    dsmig migrate-schema -v old_instancePath new_instancePath

    dsmig migrate-config -v old_instancePath new_instancePath

    dsmig migrate-security -v old_instancePath new_instancePath

    dsmig migrate-data -v old_instancePath new_instancePath


    Notes

    • If the dsmig 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 dsmig command again.
    • If the Directory Server instance you're migrating is storing configuration data for other Java ES components, for example for the Sun Java Communications Suite Messaging Server component, it might be required that you migrate a specific part of the directory information tree named o=netscaperoot. This root suffix is not migrated by default. To migrate o=netscaperoot, use the -N option of the dsmig migrate-config and dsmig migrate-data commands. For example:

      dsmig migrate-config -N -v old_instancePath     new_instancePath

    • If you are migrating from an instance on a 32-bit architecture to one on a 64-bit architecture, you cannot use the dsmig migrate-data command (automatic migration tool). You have to migrate the data manually, as documented in the Migration Guide referenced below. However you can still perform automatic migration of schema, configuration, and security data.
    • In some cases, when starting Directory Server after migrating directory data, Release 5U1 error checking detects circular definitions in Directory Server group entries. These circular definitions are functionally benign, but can result in a large number of errors being logged into the error file.

    For details of the migration process, the dsmig commands, and manual migration, see the Directory Server Enterprise Edition 6 Migration Guide, http://docs.sun.com/doc/819-0994.

Verifying the Upgrade

You can verify successful upgrade of Directory Server as follows.

  1. Check the current version of Directory Server:
  2. DirServer-base/ds6/bin/dsadm -V

    See Table 5-4 for output values.

  3. Check the startup messages in the Directory Server error log:
  4. instancePath/logs/errors


    Note

    At startup, Release 5U1 Directory Server detects circular definitions in the Directory Server group entries. 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

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure, except that 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 5U1 upgrade is achieved by reverting to the previous version, which is left intact by the upgrade to Release 5U1.

Multiple Instance Upgrades

The procedures in Release 4 Directory Server Upgrade do not explicitly deal with deployment architectures in which Directory Server is replicated for availability or scalability. These architectures might include Directory Server replication or the deployment of Directory Server as a data service in a Sun Cluster environment.

Rolling Upgrades of Directory Server Replicates

Multiple instances of Directory Server on different computer systems, such as used in multi-master replication deployment architectures, can be sequentially upgraded one instance at a time. After first synchronizing all Directory Server masters, you upgrade each instance on its respective host computer while the other instances are left running. This rolling upgrade allows the directory service to remain online while the individual Directory Server instances that provide the service are being upgraded.

Upgrading Directory Server as a Data Service

Information regarding upgrade and roll back of Directory Server as a data service in a Sun Cluster environment is currently under development.


Upgrading Directory Server from Java ES Release 3

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

To upgrade Release 3 Directory Server to Release 5U1, use the instructions in Upgrading Directory Server from Java ES Release 4, except substitute Release 3 wherever Release 4 is referenced.


Upgrading Directory Server from Java ES Release 2

Java ES certifies indirect upgrade from Java ES 2004Q2 (Release 2) Directory Server by first upgrading to Release 5 Directory 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 Server to Release 5U1 Directory Server (as documented in Upgrading Directory Server from Java ES 5).

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

Instructions for upgrading Java ES shared components to Release 5U1 are provided in Chapter 2, "Upgrading Java ES Shared Components".

To directly upgrade Release 2 Directory Server to Release 5U1, use the instructions in Upgrading Directory Server from Java ES Release 4, except substitute Release 2 wherever Release 4 is referenced.


Note

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




Previous      Contents      Index      Next     


Part No: 820-2510-10
November 2007.   Copyright 2004 Sun Microsystems, Inc. All rights reserved.