Chapter 2 Installation Notes

This chapter tells you where to download Directory Server Enterprise Edition software, and lists primary installation requirements.

This chapter includes the following sections:

• Support Services and Licenses

• What's New in Directory Server Enterprise Edition 6.3.1

• Getting the Software

• Hardware Requirements

• Operating System Requirements

• Software Dependency Requirements

• Installation Privileges and Credentials

• Installation Instructions

• Uninstallation Instructions

Refer to the Sun Directory Services blog for the most current information about the Directory product line.

The Sun Java System Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02 must be applied on top of a Directory Server Enterprise Edition 6.3.1 ZIP installation. For directions see Installing Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02.

The Sun Java System Directory Server 6.3.1 Security Patch 143463-01 must be applied on top of Directory Server Enterprise Edition 6.3.1 installation. For directions see Installing Directory Server Enterprise Edition 6.3.1 Security Patch 143463-01.

Sun Directory Proxy Server 6.3.1 update 1 patch 141958–01 is designed to be applied on top of Directory Server Enterprise Edition 6.3.1 to fix issues in the Directory Proxy Server component. For more information, refer to Directory Proxy Server 6.3.1 Update 1.

Support Services and Licenses

Before you start with the product installation, make sure you read the support and licensing information thoroughly.

Support Services

Sun Software Service Standard, Premium and Premium Plus plan offerings are available for Sun Java System Directory Server Enterprise Edition and can be purchased either through a Sun sales representative, an authorized Sun reseller, or online at http://www.sun.com/sales/index.jsp. These service plans include telephone and online technical support, on-demand software updates, online system administration resources, support notification services and one-stop interoperability assistance (Premium and Premium Plus plans only). In addition, the Premium Plus plan features a customer advocate and a customer-focused support team.

For complete feature set information, visit: http://www.oracle.com/support/premier/index.html

You may access the service lists describing all Sun service program offerings at: http://www.sun.com/servicelist

Licenses for Directory Server Enterprise Edition Managed Entries

Licenses are provided based on the number of entries you plan to manage using Directory Server Enterprise Edition. After a license is provided, you can replicate the entries as many times as required to get maximum flexibility out of your directory implementation. The only condition is that you do not change any of the replicated entries and store all of the replicated entries on the same operating system. If the replicated entries are stored on any other operating system, you must purchase a license for those entries.

Previous Solaris licences provided 200,000 free entries for Directory Server. In this case, the licences covered only the core directory server component, not the other Directory Server Enterprise Edition components. You can still purchase an upgrade from core directory server component to full Directory Server Enterprise Edition. To get support for those 200,000 Directory Server entries, a Software Service Plan for Directory Server must be purchased. The Solaris Service Plan does not cover those entries.

You can review the latest license for a given version of a product before downloading it from http://www.sun.com/software/products/directory_srvr_ee/get.jsp.

What's New in Directory Server Enterprise Edition 6.3.1

Directory Server Enterprise Edition 6.3.1 is a patch release that corrects issues known in the Directory Server Enterprise Edition releases 6.0 through 6.3. This release does not add new features to the Directory Server Enterprise Edition releases 6.0 through 6.3.

Getting the Software

Directory Server Enterprise Edition 6.3.1 is a maintenance release that is applied to an existing installation of Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3. You can download Sun Java System Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 software from the following location.

http://www.sun.com/software/products/directory_srvr_ee/get.jsp

The download page serves as a starting point to direct you to the proper downloads depending on the distribution type you need to download. Directory Server Enterprise Edition 6.3.1 is available in the following distributions.

• Native package distribution

• Zip distribution

Directory Server Enterprise Edition 6.3.1 is available in the following forms.

• Native patch – patches to upgrade Directory Server Enterprise Edition 6.0, 6.1, 6.2, and 6.3 native packages installed using the Java ES installer.

• Zip based distribution – patches to Directory Server Enterprise Edition 6.0, 6.1, 6.2, and 6.3 zip installations.

Directory Server Enterprise Edition 6.3.1 patches are available through SunSolve.For information on patch numbers, see Installation Instructions.

For the detailed information on what you need to install based on your current installation, refer to Installation Instructions.

Hardware Requirements

This section covers hardware requirements for Directory Server Enterprise Edition component products.

• Directory Server Hardware Requirements

• Directory Proxy Server Hardware Requirements

Directory Server Hardware Requirements

Directory Server software requires the following hardware.

Directory Proxy Server Hardware Requirements

Directory Proxy Server software requires the following hardware.

Operating System Requirements

This section covers operating systems, patches and service packs required to support Directory Server Enterprise Edition component products.

Directory Server, Directory Proxy Server, and Directory Server Resource Kit Operating System Requirements

Directory Server, Directory Proxy Server, and Directory Server Resource Kit share the same operating system requirements. The Directory Server Enterprise Edition software has been validated with full installations of the operating systems listed here, not with reduced “base”, “End User”, or “core” installations. Certain operating systems require additional service packs or patches as shown in the following table.

For all supported versions of Microsoft Windows, Directory Server and Directory Proxy Server run only in 32–bit mode, and the filesystem type must be NTFS.

To avoid downloading most individual patches, obtain Solaris patch clusters . To obtain Solaris patch clusters, follow these steps:

1. Go to the SunSolve patch page at http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage.

2. Click the Recommended Patch Clusters link.

3. Download the patch cluster for your Solaris OS and Java ES versions.

Note that installations on SuSE Linux Enterprise Server require you to reset several Java environment variables. See Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide for more details.

Software Dependency Requirements

Directory Server relies on the Network Security Services, NSS, layer for cryptographic algorithms. NSS has been validated to work with the Sun cryptographic framework provided on Solaris 10 systems, which supports cryptographic acceleration devices.

On Microsoft Windows systems, Directory Server requires ActivePerl software to use account activation and manual schema replication commands. Directory Server Enterprise Edition does not provide ActivePerl. The dependency concerns the following commands.

• ns-accountstatus(1M)

• ns-activate(1M)

• ns-inactivate(1M)

• schema_push(1M)

On Microsoft Windows systems, you must disable the pop-up blocker to make Directory Service Control Center work properly.

The Directory Service Control Center supports the following application servers:

• Sun Java System Application Server 8.2.

• Tomcat 5.5.

For more information, see Installing Directory Service Control Center From Zip Distribution in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

Directory Proxy Server will work with any LDAPv3 compliant directory servers, but it is tested only with Sun Java System Directory Server.

For virtualization, Directory Proxy Server has been validated with the following JDBC data sources, using the drivers mentioned below.

On Microsoft Windows systems, the dsee_deploy command cannot properly register software with the Common Agent Container, cacao, when you run the command from an MKS shell. This can occur when your MKS PATH does not include the system-drive:\system32 folder. Alternatively, run the command on the Microsoft Windows native command line.

On Solaris 10, rc.scripts are deprecated so commands like dsadm autostart are not supported. Instead use Solaris 10 Service Management Facility (SMF) to handle these types of requests. For example, dsadm enable-service. For more information on SMF, see the Solaris operating system documentation.

Connector Requirements

All connectors must be able to communicate with Message Queue.

In addition, the following connector requirements must be met.

• The Active Directory connector must be able to access the Active Directory Domain Controller over LDAP, port 389, or LDAPS, port 636.

• The Directory Server connector must be able to access Directory Server instances over LDAP, default port 389, or LDAPS, default port 636.

Directory Server Plug-in Requirements in a Firewall Environment

Each Directory Server plug-in must be able to reach the Directory Server connector’s server port, which was chosen when the connector was installed. Plug-ins that run in Directory Server Master replicas must be able to connect to Active Directory’s LDAP, port 389, or LDAPS, port 636. The plug-ins that run in other Directory Server replicas must be able to reach the master Directory Server LDAP and LDAPS ports.

Supported Browsers for Directory Service Control Center

The following table displays the browsers for each operating system that supports Directory Service Control Center.

Installation Privileges and Credentials

This section covers privileges or credentials required for installation of Directory Server Enterprise Edition component products.

• Directory Server, Directory Proxy Server, Directory Service Control Center, and Directory Server Resource Kit Privileges

Directory Server, Directory Proxy Server, Directory Service Control Center, and Directory Server Resource Kit Privileges

You must have the following privileges when installing Directory Server, Directory Proxy Server, or Directory Service Control Center from the Java Enterprise System native package based distribution.

• On Solaris and Red Hat systems, you must install as root.

• On Windows systems, you must install as Administrator.

You can install Directory Server, Directory Proxy Server, and Directory Server Resource Kit from the zip distribution without special privileges. See the Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide for details.

Before You Upgrade

You must consider the following points before applying the Directory Server Enterprise Edition 6.3.1 patch.

• Native package based distribution. All Directory Server and Directory Proxy Server instances, including the DSCC registry, must be stopped before the Directory Server Enterprise Edition 6.3.1 patch is applied.

  If you apply the patch without stopping the server instances, the instances might crash the next time you restart them.

  ---

  Note –

  On Windows, the following dsadm command fails to stop the DSCC registry.

  dsadm.exe stop C:\Program Files\Sun\JavaES5\DSEE\var\dscc6\dcc\ads

  As a workaround, kill the bin_slapd.exe process using Task Manager and login as Administrator. You can now start and stop the DSCC registry successfully. The owner of the DSCC registry remains the same, that is, SYSTEM.

  For native package based distribution: after applying patches to upgrade Directory Server Enterprise Edition, you must restart Sun Web Console using the following command:

  # smcwebserver restart

  ---

  To use the localized console, apply the Directory Server Enterprise Edition 6.3 localized patch (if it is not already applied) before the Directory Server Enterprise Edition 6.3 core patch. If you apply the 6.3.1 core patch before applying the 6.3 localization patch, then run the following commands in the specified order.

  # dsccsetup console-unreg # dsccsetup console-reg

  For more information, see bug 6583131 in Known Directory Server Issues in 6.3.1.

• Zip based distribution. All Directory Server and Directory Proxy Server instances must be stopped before the Directory Server Enterprise Edition 6.3.1 zip distribution is applied on top of one of the applicable zip installations:

  • Directory Server Enterprise Edition 6.0

  • Directory Server Enterprise Edition 6.1

  • Directory Server Enterprise Edition 6.2

  • Directory Server Enterprise Edition 6.3

  This check is done by the dsee_deploy command itself, but is not performed on the Microsoft Windows 2000 platform. For more information, see 6660462 in Known Directory Server Issues in 6.3.1.

  If you apply the patch without stopping the server instances, the instances might crash the next time you restart them.

  Note that the patchzip is not applied to the Directory Service Control Center until you undeploy and then redeploy the WAR file. This requirement is related to bug 6583131 in Known Directory Server Issues in 6.3.1.

Installation Instructions

Directory Server Enterprise Edition 6.3.1 is a maintenance release that delivers bug fixes mainly for Directory Service Control Center, Directory Proxy Server, and Directory Server. Only the upgrade mode is offered within 6.3.1 using Native Packages or ZIP distribution.

If you plan to install Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 please refer to the Sun Java System Directory Server Enterprise Edition Installation Guide for 6.0, 6.1, 6.2, or 6.3. See Directory Server Enterprise Edition Documentation Set.

These installation instructions provide step-by-step instructions for installing Directory Service Control Center, Directory Proxy Server, Directory Server, Directory Server Resource Kit, and Identity Synchronization for Windows components of Directory Server Enterprise Edition.

The Sun Java System Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02 must be applied on top of a Directory Server Enterprise Edition 6.3.1 ZIP installation. For directions see Installing Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02.

This guide does not cover installation with other Java Enterprise System (Java ES) products. If you plan to install Directory Server and Directory Service Control Center software with other Java ES software, read the installation instructions for Java ES software at http://docs.sun.com/coll/1286.3. For Microsoft Windows, read the installation instructions for Java ES software at Java Enterprise System 5 for Microsoft Windows.

This section covers the following parts.

• Upgrading Directory Server Enterprise Edition to 6.3.1 Using Native Packages

• Upgrading Directory Server Enterprise Edition to 6.3.1 Using ZIP distribution

The following table identifies information for you to use to upgrade Directory Server Enterprise Edition to version 6.3.1 based on your current installation and the type of distribution you are using.

In general, it is a good practice to back up the directory databases regularly and particularly before upgrading the directory server. See the Sun Java System Directory Server Enterprise Edition 6.3 Administration Guide for information about backing up the database.

Upgrading Directory Server Enterprise Edition to 6.3.1 Using Native Packages

To Upgrade Shared Components Using Patches

Before You Begin

Before upgrading Directory Server Enterprise Edition to 6.3.1 using native packages, you must upgrade the shared components. On Solaris and Red Hat systems you must be root, on Windows systems, you must be Administrator to perform this procedure.

Using patches, you can upgrade shared components on Solaris, Linux, and Windows. On Linux, to install patches you must use installpatch. The installpatch script is delivered with the patch.

Select the platform as per your requirements and install all the patches specified for that platform. If newer patch revisions become available, use the newer ones instead of those shown in the table.

Choose the right NSS/NSPR/JSS patch for your system by getting the package version of SUNWpr and SUNtls on your system.

# pkginfo -l SUNWpr | grep VERSION
# pkginfo -l SUNWtls | grep VERSION    

Then choose the right patch series from the table below.

The following table lists the Shared Components patches for Windows platform.

Before upgrading Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 to 6.3.1, you need to upgrade the shared components.

1. Shut down any processes using the shared components.

2. If applicable, shut down the shared components.

3. Obtain the latest upgrade patches as shown in the tables above.

   For more information on how to obtain the patches, see Getting the Software.

4. Apply the appropriate patches for the shared components.

   Read the README.patchID file for detailed patch installation procedures.

5. Verify that the patch upgrades were successful.

   Read the README.patchID file for verification procedure.

6. If applicable, restart the shared components.

7. To Upgrade the Common Agent Container shared component on Windows, run the following commands in the same order as listed below:

   # cacaoadm prepare-uninstall # 126183-04.exe # cacao-install-path\share\cacao_2\configure.bat # cacao-install-path\share\cacao_2\bin\cacaoadm rebuild-dependencies

8. If your installation uses Identity Synchronization for Windows and you have applied the latest NSS patch 3.12 on your system, set symbolic links to the new libraries delivered in NSS patch 3.12, as shown in the following example. The default value of the SERVER_ROOT path name is /var/mps/serverroot.

   $ cd /var/mps/serverroot/lib $ ln -s /usr/lib/mps/secv1/libnssdbm3.so libnssdbm3.so $ ln -s /usr/lib/mps/secv1/libnssutil3.so libnssutil3.so $ ln -s /usr/lib/mps/secv1/libsqlite3.so libsqlite3.so $ cd /var/mps/serverroot/lib/sparcv9 $ ln -s /usr/lib/mps/secv1/sparcv9/libnssdbm3.so libnssdbm3.so $ ln -s /usr/lib/mps/secv1/sparcv9/libnssutil3.so libnssutil3.so $ ln -s /usr/lib/mps/secv1/sparcv9/libsqlite3.so libsqlite3.so

To Upgrade Directory Server Enterprise Edition Using Native Packages

Before You Begin

Make sure all the shared components are up-to-date. For more information, see To Upgrade Shared Components Using Patches.

If you already have Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 installed, upgrade to version 6.3.1 using the following procedure.

On Solaris and Red Hat systems, you must be root to perform these steps and Administrator on Windows systems.

All the Directory Server instances, Directory Proxy Server instances, and configuration information remain unaffected after you complete the Directory Server Enterprise Edition upgrade.

The following table displays the patch numbers that are required to upgrade Directory Server Enterprise Edition on different platforms. If newer patch revisions become available, use the newer ones instead of those shown in the table.

To make the localized Directory Server Enterprise Edition work successfully, install the localized patches before installing the core patches.

Each localization patch contains all the supported languages for the selected platform.

1. Stop the DSCC registry.

   • On Solaris

     # dsadm stop /var/opt/SUNWdsee/dscc6/dcc/ads

   • On Linux

     # dsadm stop /var/opt/sun/dscc6/dcc/ads

   • On Windows, the following dsadm command fails to stop the DSCC registry.

     dsadm.exe stop C:\Program Files\Sun\JavaES5\DSEE\var\dscc6\dcc\ads

     As a workaround, kill the bin_slapd.exe process using Task Manager, and log in as Administrator. You can now start and stop the DSCC registry successfully. The owner of the DSCC registry remains the same, that is, SYSTEM.

2. Stop any running instances of Directory Server and Directory Proxy Server.

3. Upgrade the shared components. See To Upgrade Shared Components Using Patches.

4. Download the Directory Server Enterprise Edition 6.3.1 patch.

   See Getting the Software for more details.

5. Change to the directory where you have saved the patch listed in the preceding table.

6. Run the following command to install the patch.

   • Solaris OS

     Before upgrading Directory Server Enterprise Edition, you must install 119254-38 on Solaris 10 SPARC and 119255-38 on Solaris 10 x86. See Getting the Software for information on downloading patches.

     Alternatively, use -G with the patchadd command on Solaris 10 SPARC and Solaris 10 x86 while applying the Directory Server Enterprise Edition upgrade patch. For example:

     # patchadd -G patch-id

     For other versions of Solaris, use the following command:

     # patchadd patch-id

   • Linux

     1. Open the directory where the installpatch file is located.

     2. Run installpatch.

        # ./installpatch

   • Windows

     1. Open the folder where the patch-id.exe executable file is located.

     2. Double-click patch-id.exe.

     3. After the successful installation of the patch, run the following commands:

        # dsccsetup console-unreg # dsccsetup console-reg

7. Start the Directory Server instances and Directory Proxy Server instances, if any.

8. Start Web Console and Common Agent Container.

9. Restart the DSCC registry.

   • On Solaris

     # dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads

   • On Linux

     # dsadm start /var/opt/sun/dscc6/dcc/ads

   • On Windows

     dsadm.exe start C:\Program Files\Sun\JavaES5\DSEE\var\dscc6\dcc\ads

Upgrading Directory Server Enterprise Edition to 6.3.1 Using ZIP distribution

To Upgrade Directory Server Enterprise Edition to 6.3.1 Using ZIP Distribution

Before You Begin

Back up the Directory Server Enterprise Edition installation directory, if any, before upgrading to Directory Server Enterprise Edition 6.3.1, as later you will not be able to restore any previous Directory Server Enterprise Edition installation.

You can install the zip distribution as a non-root user.

The dsee_deploy command automatically updates the installation if it finds any previous installation. However, in the case of SuSE Linux 9 and HP-UX, before you upgrade the Directory Server Enterprise Edition installation, you must first upgrade the operating system to SuSE Linux 9 SP4 and HP-UX 11.23 respectively. Then use following procedure to upgrade your Directory Server Enterprise Edition installation to 6.3.1.

1. Stop CACAO and any running instances of Directory Server and Directory Proxy Server associated with the installation that you intend to patch. Also stop the application server that hosts the WAR file and the DSCC registry.

2. If the system you are upgrading is hosted on SuSE Linux 9 or HP-UX, upgrade your operating system.

   • Upgrade SuSE Linux 9 SP3 to SuSE Linux 9 SP4.

     On SuSE 64-bit, .pam-32bit-9-yyyymmddhhmm.rpm is a prerequisite for CACAO to start, and you must install it if it is not already present on your system.

   • Because Directory Server Enterprise Edition 6.0 and 6.1 support only HP-UX 11.11, you must upgrade your operating system to HP-UX 11.23 before upgrading Directory Server Enterprise Edition to 6.3.1.

   Refer to the operating system documentation for information about how to upgrade the operating system, how to preserve the partition where Directory Server Enterprise Edition is installed, and where to get the latest patch bundles.

3. Upgrade Directory Server Enterprise Edition to 6.3.1

   1. Use the dsee_deploy command from Directory Server Enterprise Edition 6.3.1 zip distribution, with the same installation path, and CACAO port used your previous installation of Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3. The dsee_deploy command will restart CACAO and DSCC registry.

      1. Obtain the zip distribution for this installation.

         Refer to the following table for information about the appropriate zip patch for your system. If newer patch revisions become available, use the newer ones instead of those shown in the table.

         All the multilingual files are included in the above mentioned patches.

         Operating System	Patch number
         Solaris SPARC	126748-05
         Solaris 9 x86	126749-05
         Solaris 10 x86 and AMD x64	126750-05
         Red Hat Linux	126751-05
         SuSE Linux	126751-05
         HP-UX	126752-05
         Windows	126753-05

      2. Install the prerequisite patches or service packs for your platform, as described in Operating System Requirements.

      3. Change to the zip distribution directory that contains the dsee_deploy command.

      4. Upgrade your Directory Server Enterprise Edition installation currently installed at install_path with the dsee_deploy(1M) command.

         $ ./dsee_deploy install -i install-path options

         On Windows installations, browse to the zip distribution folder that contains the dsee_deploy command and run the following command:

         dsee_deploy install -i install-path options

         For example, the following command upgrades your existing Directory Server Enterprise Edition previously installed at /local directory, assuming that you have write access to the directory.

         $ ./dsee_deploy install -i /local

         You can also use the --no-inter option to install in non-interactive mode, accepting the license without confirmation. Non-interactive mode is particularly useful for silent installation.

         During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which when deployed with the application server enables you to access and manage the server instances through web console. The functionality is similar to DSCC in native packages. For more information about the WAR file, see Installing Directory Service Control Center From Zip Distribution in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

         During the installation process, the multilingual packages are also installed.

      5. Deploy the latest dscc.war file in the application server

         For step-by- step information, refer to Installing Directory Service Control Center From Zip Distribution in Sun Java System Directory Server Enterprise Edition 6.3 Installation Guide.

      6. Restart Directory Server and Directory Proxy Server instances and the application server for WAR file.

4. Start daemons only when both operating system and Directory Server Enterprise Edition are upgraded.

Installing Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02

The Sun Java System Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02 must be applied on top of a Directory Server Enterprise Edition 6.3.1 ZIP installation. This patch delivers NSS 3.12.5 as well as SASL 2.19.20090601.

This patch cannot be applied to versions of Directory Server Enterprise Edition earlier than 6.3.1. For directions to upgrade to version 6.3.1, see Table 2–1.

To install Directory Server Enterprise Edition 6.3.1 Security Patchzip 142807-02, download it from http://sunsolve.sun.com and follow the installation instructions provided in the README file.

Installing Directory Server Enterprise Edition 6.3.1 Security Patch 143463-01

The Sun Java System Directory Server 6.3.1 Security Patch 143463-01 must be applied on top of a Directory Server Enterprise Edition 6.3.1 installation.

This patch cannot be applied to versions of Directory Server Enterprise Edition earlier than 6.3.1. For directions to upgrade to version 6.3.1, see Table 2–1.

To install Directory Server Enterprise Edition 6.3.1 Security Patch 143463-01, download it from http://sunsolve.sun.com and follow the installation instructions provided in the README file.

Confirm that the installation of patch 143463-01 is successful by running this command and verifying that the response is the same as shown here:

./dsadm -V
[dsadm]
dsadm               : 6.3.1                B2008.1121.0156 ZIP

[slapd 64-bit]
Sun Microsystems, Inc.
Sun-Java(tm)-System-Directory/6.3.1_sec B2010.0201.1612 64-bit
ns-slapd            : 6.3.1                B2008.1121.0156 ZIP
Slapd Library       : 6.3.1_sec            B2010.0201.1612
Front-End Library   : 6.3.1                B2008.1121.0156

Uninstallation Instructions

If you plan to uninstall Directory Server Enterprise Edition 6.0, 6.1, 6.2, or 6.3 please refer to the chapter 3. "Uninstalling Directory Server Enterprise Edition" of Sun Java System Directory Server Enterprise Edition Installation Guide for 6.0, 6.1, 6.2, or 6.3. See theDirectory Server Enterprise Edition Documentation Set.

This section describes the following topics:

• Downgrading from Directory Server Enterprise Edition 6.3.1 Using Native Packages

• Downgrading from Directory Server Enterprise Edition 6.3.1 Using ZIP Distribution

Downgrading from Directory Server Enterprise Edition 6.3.1 Using Native Packages

After you upgrade to Directory Server Enterprise Edition 6.3.1 you might want to restore your previous Directory Server Enterprise Edition installation. This section provides complete information about how to downgrade the Directory Server Enterprise Edition installation.

To Downgrade Directory Server Enterprise Edition Using Native Package

Downgrading Directory Server Enterprise Edition restores the previous working copy of your Directory Server Enterprise Edition installation and retains all your configuration information that you had before upgrading to Directory Server Enterprise Edition 6.3.1.

1. Stop all running server instances.

2. Run the following command to remove the patch.

   Remove the localization patch before you remove the base patch to clean up the system. Refer to Patch Table for Native Package in Upgrading Directory Server Enterprise Edition to 6.3.1 Using Native Packages for the patch ID for each platform.

   • Solaris

     # patchrm patch-id

   • Linux

     Go to the directory where the Directory Server Enterprise Edition 6.3, 6.2, 6.1, or 6.0 .rpm files are stored and run the following command repetitively for all the rpm files as specified in the table below. The set of rpm files that you choose depends on the previous installation of Directory Server Enterprise Edition you had.

     Make sure that after downgrading you have all the 6.0, 6.1, 6.2, or 6.3 rpm files. Downgrading the subset of the rpm files results in corrupted installation.

     Localized 6.3 rpm files	sun-ldap-console-gui-l10n-6.3-1.i386.rpm sun-ldap-console-gui-help-l10n-6.3-1.i386.rpm sun-ldap-proxy-client-l10n-6.3-1.i386.rpm sun-ldap-proxy-l10n-6.3-1.i386.rpm sun-ldap-directory-client-l10n-6.3-1.i386.rpm sun-ldap-directory-l10n-6.3-1.i386.rpm sun-ldap-shared-l10n-6.3-1.i386.rpm
     Base 6.3 rpm files	sun-ldap-console-gui-6.3-7.i386.rpm sun-ldap-console-gui-help-6.3-7.i386.rpm sun-ldap-console-agent-6.3-7.i386.rpm sun-ldap-console-cli-6.3-7.i386.rpm sun-ldap-console-common-6.3-7.i386.rpm sun-ldap-proxy-man-6.3-7.i386.rpm sun-ldap-proxy-client-6.3-7.i386.rpm sun-ldap-proxy-config-6.3-7.i386.rpm sun-ldap-proxy-6.3-7.i386.rpm sun-ldap-directory-man-6.3-7.i386.rpm sun-ldap-directory-client-6.3-7.i386.rpm sun-ldap-directory-config-6.3-7.i386.rpm sun-ldap-directory-dev-6.3-7.i386.rpm sun-ldap-directory-6.3-7.i386.rpm sun-ldap-shared-6.3-7.i386.rpm
     Localized 6.2 rpm files	sun-ldap-console-gui-l10n-6.2-6.i386.rpm sun-ldap-console-gui-help-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-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
     Base 6.2 rpm files	sun-ldap-console-gui-6.2-5.i386.rpm sun-ldap-console-gui-help-6.2-5.i386.rpm sun-ldap-console-agent-6.2-5.i386.rpm sun-ldap-console-cli-6.2-5.i386.rpm sun-ldap-proxy-man-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-6.2-5.i386.rpm sun-ldap-directory-man-6.2-5.i386.rpm sun-ldap-directory-client-6.2-4.i386.rpm sun-ldap-directory-config-6.2-5.i386.rpm sun-ldap-directory-6.2-5.i386.rpm sun-ldap-shared-6.2-5.i386.rpm
     Localized 6.1 rpm files	sun-ldap-console-gui-l10n-6.1-3.i386.rpm sun-ldap-console-gui-help-l10n-6.1-3.i386.rpm sun-ldap-proxy-client-l10n-6.1-3.i386.rpm sun-ldap-proxy-l10n-6.1-3.i386.rpm sun-ldap-directory-client-l10n-6.1-3.i386.rpm sun-ldap-directory-l10n-6.1-3.i386.rpm sun-ldap-shared-l10n-6.1-3.i386.rpm
     Base 6.1 rpm files	sun-ldap-console-gui-6.1-2.i386.rpm sun-ldap-console-gui-help-6.1-2.i386.rpm sun-ldap-console-agent-6.1-2.i386.rpm sun-ldap-console-cli-6.1-2.i386.rpm sun-ldap-proxy-man-6.1-2.i386.rpm sun-ldap-proxy-client-6.1-2.i386.rpm sun-ldap-proxy-config-6.1-2.i386.rpm sun-ldap-proxy-6.1-2.i386.rpm sun-ldap-directory-man-6.1-2.i386.rpm sun-ldap-directory-client-6.1-2.i386.rpm sun-ldap-directory-config-6.1-2.i386.rpm sun-ldap-directory-6.1-2.i386.rpm sun-ldap-shared-6.1-2.i386.rpm

   • Windows

     1. Run the dsccsetup dismantle command to dismantle the DSCC.

     2. Double-click the Uninstall_patch-id.bat file to remove the patch. The Uninstall_patch-id.bat file is stored in the folder where the patch is saved.

     3. Downgrade Common Agent Container. See the uninstallation steps in the 126183-04 patch README.

        1. Run the cacaoadm prepare-uninstall command.

        2. Double-click Uninstall_126183-04.bat to remove the patch

Downgrading from Directory Server Enterprise Edition 6.3.1 Using ZIP Distribution

Directory Server Enterprise Edition 6.3.1 installation does not downgrade to the previous version. If you need to revert to the previous Directory Server Enterprise Edition version, restore the backup copy that you saved before upgrading to Directory Server Enterprise Edition 6.3.1.

To remove Directory Server Enterprise Edition completely, refer to 6.3 Installation Guide chapter “To Remove Software Installed From the Zip Distribution” in the Directory Server Enterprise Edition 6.3 Installation Guide.