This section describes how to perform an upgrade of Web Server from Java ES 5 to Java ES 5 Update 1. This section covers the following topics:
Before you upgrade Web Server, perform the tasks described below.
Verify the current version of Web Server before you upgrade.
Examine the subcomponent error log at:
The Web Server version information is as follows.
Sun Java System Web Server 7.0 U1
Sun Java System Web Server 7.0
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Release 5U1 Web Server has no hard upgrade dependencies, but upgrade is only certified when shared components have also been upgraded. The upgrade from Release 5 to Release 5U1 requires that Windows Installer patch (126910–02) is already applied.
The Web Server upgrade from Release 5 to Release 5U1 does not modify the Release 5 configuration data. You do not need to back up current data.
This section discusses considerations that impact the upgrade procedure for Web Server, followed by a description of the procedure itself.
The upgrade of Web Server software to Java ES Release 5U1 takes into account the following considerations:
In a deployment architecture in which there are multiple instances of Web Server running on a single computer (all corresponding to the same installed Web Server image), you only have to upgrade the Web Server image once.
In a maintenance upgrade, you do not have to migrate schema, configuration, security or user data.
The Release 5U1 Web Server upgrade patches for Windows are shown in the following table:
Web Server core
Web Server localization
The localized patch files are delivered within the core patch.
The procedure documented below applies to Web Server instances residing locally on the computer where the upgrade is taking place.
Log in as administrator.
Shut down the Release 5 Web Server instances and the administration server.
Choose Start > Sun Java Enterprise System 5 > Web Server 7.0 > Administration Console.
The Web Server 7.0 Administration Server Login page appears.
Type the User Name and Password, then click OK.
The Web Server 7.0 Administration Server page appears.
Select a Server from the drop down list, and click Manage.
The Server Manager page appears.
Click Server Off.
Using the Command-Line Interface:
To stop the Web Server instance, change to WebServer-base\https-hostName.domainName\bin.
Run the stopserv.bat command.
Make sure you have upgraded any Java ES components upon which Web Server has hard upgrade dependencies (see Upgrade Web Server Dependencies.
Obtain the required Web Server Release 5U1 upgrade patches, based on Table 5–4.
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 Server instances and the administration server.
You can verify successful upgrade of Web Server by examining the subcomponent error logs at:
The messages that indicate the Java ES release version are:
Sun Java System Web Server 7.0 U1 (Build Date Time)
Sun Java System Web Server 7.0 (Build Date Time)
There are no post-upgrade tasks beyond the steps described in Upgrade Considerations.
Log in as administrator.
Shut down the Web Server instances and the administration server.
Double-click Uninstall_patch-id.bat to uninstall the patch.
Restart the administration server and the Web Server instances that were shut down in step 2.