This section discusses considerations that impact the upgrade procedure for Directory Server, followed by a description of the procedure itself.
This upgrade of Directory Server software to Release 5U1 takes into account the following considerations:
Any Java ES components or applications using a Directory Server instance should be shut down if performing LDAP queries during the Directory Server upgrade or if using a library that is being patched.
In a deployment architecture in which there are multiple instances of Directory Server running on a single computer (all corresponding to the same installed Directory Server image), you only have to upgrade the Directory Server image once.
In a maintenance upgrade, you do not have to migrate schema, configuration, security and user data.
The Release 5U1 Directory Server upgrade patches for Windows OS are shown in the following table:
Directory Server Enterprise Edition core (includes Directory Server)
Directory Server localization
The localized patch files are delivered within the core patch.
The procedure documented below applies to Directory Server instances residing locally on the computer where the upgrade is taking place.
Log in as administrator.
Stop any Java ES components which use the Directory Server.
Stop the service using persistent connections like Access Manager. You can stop Access Manager by stopping its web container.
Shut down the Directory Server.
Also shut down Directory Proxy Server and Directory Registry if they are on the same system.
DSEE-base\ds6\bin\dsadm.exe stop instancePath
DSEE-base\dps6\bin\dpadm.exe stop instancePath
DSEE-base\dscc6\bin\dsccsetup.exe stop instancePath
Make sure you have upgraded any Java ES components upon which Directory Server has hard upgrade dependencies (see Upgrade Directory Server Dependencies.
Obtain the required Directory Server Release 5U1 upgrade patches, based on Table 3–3.
To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to \workingDirectory.
Install the patch.
Installation is generally performed by running patch-id.exe, however, be sure to consult the README.patch-id file in the patch directory for installation instructions.
If you are prompted to restart the system, select No. Wait till the patch installation process is completed and then restart and re-login as the same user to complete the patch installation.
Verify the patch log file.
The log file is found at: %TEMP%\SUNJAVAES_<patch-id>.log
Verify the patch installation with the utility ListJavaESPatches.exe.
Run ListJavaESPatches.exe and check that the output includes the patch id of the patch that you have installed in Step 6. For more information, see Identifying Installed Java ES Patches.
Refresh DSCC application into SJWC.
This step should be performed on the system where DSCC is installed.
Start the Directory Server.
Also start Directory Proxy Server and Directory Registry if they are on the same system.
DSEE-base\ds6\bin\dsadm.exe start instancePath
DSEE-base\dps6\bin\dpadm.exe start instancePath
DSEE-base\dscc6\bin\dsccsetup.exe start instancePath
Start any Java ES components that use Directory Server.