This section includes information about upgrading Web Proxy Server from Java ES 5 to Java ES 5 Update 1 . The section covers the following topics:
When upgrading Release 5 Web Proxy Server to Release 5U1, consider the following aspects of the upgrade process:
General Upgrade Approach. The upgrade is performed using patches. There is no additional reconfiguration required.
Upgrade Dependencies. Web Proxy Server has dependencies on a number of Java ES shared components (see Table 1–8).
Backward Compatibility. Release 5UI Web Proxy Server is backwardly compatible with the Release 5 version.
Upgrade Rollback. Rollback of the Release 5U1 upgrade of Web Proxy Server is achieved by removing the upgrade patches.
This section describes how to perform an upgrade of Web Proxy Server from Java ES 5 to Java ES 5 Update 1. This section covers the following topics:
Before you upgrade Web Proxy Server, perform the tasks described below.
Verify the current version of Web Proxy Server before you upgrade.
Examine the subcomponent error log at:
The Web Proxy Server version information is as follows.
Sun Java System Web Proxy Server 4.0.5 (Build Date)
Sun Java System Web Proxy Server 4.0.4 (Build Date)
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. However, the upgrade of Web Proxy Server to Release 5U1 only requires that Windows Installer patch (126910–02) is already applied.
The Web Proxy Server upgrade to Release 5U1 does not modify the Release 5 configuration data. There is no need to back up current data.
This section discusses considerations that impact the upgrade procedure for Web Proxy Server, followed by a description of the procedure itself.
The upgrade of Web Proxy Server software to Java ES Release 5U1 takes into account the following considerations:
All Web Proxy Server instances corresponding to the same installed Web Proxy Server image are upgraded at the same time. All such instances should be shut down when patches are being applied to the installed image.
The Release 5U1 Web Proxy Server upgrade patches for Windows are shown in the following table:
Web Proxy Server core
Web Proxy Server localization
The localized patch files are delivered within the core patch.
The procedure documented below applies to Web Proxy Server instances residing locally on the computer where the upgrade is taking place.
Log in as administrator.
Shut down the Release 5 Web Proxy Server instances and the administration server.
Make sure you have upgraded any Java ES components upon which Web Proxy Server has hard upgrade dependencies (see Upgrade Web Proxy Server Dependencies.
Obtain the required Web Proxy Server Release 5U1 upgrade patches, based on Table 11–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 5. For more information, see Identifying Installed Java ES Patches.
Start the Release 5U1 Web Proxy Server instances and the administration server.
You can verify successful upgrade of Web Proxy Server by examining the subcomponent error logs at :
The messages that indicate the Java ES release version are:
Sun Java System Web Proxy Server 4.0.5
Sun Java System Web Proxy Server 4.0.4
There are no post-upgrade tasks beyond the steps described in Upgrade Considerations.
Log in as administrator.
Shut down the Proxy Server instances and the administration server.
Double-click uninstall_patch-id.bat to uninstall the patch.
Restart the administration server and the Proxy Server instances that were shut down in step 2.