Java ES Upgrade Through Application of Patches

Maintenance upgrades of Java ES product components from Release 5 to Release 5U1 are performed component-by-component through the application of Java ES 5 Update 1 patches. Because of dependencies between Java ES components, the nature of a component upgrade can impact whether other components need to be upgraded as well.

The following sections provide information about upgrading Java ES through application of patches:

• Accessing Java ES Patches

• Upgrade Prerequisite-Java ES Windows Installer Patch

• Shared Component Upgrades

• Identifying and Stopping Processes to Avoid System Restart

• Identifying Installed Java ES Patches

• Default Installation Paths

Accessing Java ES Patches

Java ES 5 Update 1 patches can be accessed either as individual patches or as a patch cluster. You can access these patches in either of these two ways from the SunSolve web site:

• As a patch cluster named Java Enterprise System 5 Accumulated Patch Cluster Windows.

• As discrete upgrade patches, using the java_es-5 keyword to search for Java ES release 5 family patches.

---

Note –

This document captures only the information related to the patches and the patch cluster available at the time of Java ES 5 Update 1 release. New revisions of these patches might be made available in the future.

---

Upgrade Prerequisite-Java ES Windows Installer Patch

Before applying Java ES 5 Update 1 patches, be sure that the following Java ES Windows Installer patch has been installed:

126910–02 [Revision number indicated for the Java ES Windows Installer patch is the minimum required for upgrade to Release 5U1. If newer revision becomes available, use the newer one.]

Shared Component Upgrades

Java ES shared component upgrades are a necessary part of upgrading the product components that depend on them.

The upgrading of shared components does not require reconfiguration of the components, nor pre- or post-upgrade procedures. Shared component upgrades can be rolled back to their previous versions only after Java ES components depending on them are rolled back.

Identifying and Stopping Processes to Avoid System Restart

The Java ES 5 Update 1 Windows patching system requires a system restart if any of the delivered and updated shared component DLLs are in use by another application. There are various tools that can be used to find if any files related to Java ES are in use by other processes. You can stop those processes before applying the patch so that the patch installation can be completed without a system restart.

The following sections describe some of the tools.

ListDLLs and Process Explorer

ListDLLs is a command line tool . ListDLLs provides a list of DLLs that are in use and also their path. The list indicates which DLLs have a version different from their original version on the disk (such DLLs are flagged in the list). The path column in the list shows which DLLs are relocated.

ListDLLs can be downloaded from:http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ListDlls.mspx

Process Explorer is the GUI version of the ListDLLs program.

Process Explorer can be downloaded from: http://www.microsoft.com/technet/sysinternals/utilities/processexplorer.mspx

Checking the version of DLLs

To get the basic version information of DLLs, use the tool GetVers.exe .

You can download GetVers.exe from: http://support.microsoft.com/kb/167597

To get a more informative version information of DLLs, use the tool ShowVer.exe.

You can download ShowVer.exe from: http://www.codeproject.com/dll/showver.asp.

Identifying Installed Java ES Patches

You can execute the utility ListJavaESPatches.exe to identify the installed Java ES patches in the system. This utility is available as part of Java ES 5 installation and its default location is <JavaES5InstallDir>\utils\patch.

The utility ListJavaESPatches.exe is also made available through the newer versions of the Java ES 5 Update 1 patches.

Default Installation Paths

Java ES software is built for 32–bits Windows systems. However, it can be installed on both 32–bit and 64–bit Windows systems.

The installation with the Java ES 5 installer takes place on the following default location for 32–bit programs.

Table 1–7 Default Installation Paths

	Default location	Short equivalent
32–bit	C:\Program Files\Sun\...	c:\progra~1\sun
64–bit	C:\Program Files (x86)\Sun\...	c:\progra~2\sun

Short path formats are commonly used in logs.

In this guide, 32–bit long path format is used in definitions, examples and so on.