Sun Java Enterprise System Upgrade Guide for HP-UX |
Chapter 5
Web ServerThis chapter describes how to upgrade Web Server to Java ES Release 4 Web Server 6.1 2005Q4 SP5. The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4.
Overview of Web Server UpgradesThis section describes the following general aspects of Web Server that impact upgrading to Java ES Release 4:
About Java ES Release 4 Web Server
Java ES Release 4 versions of Web Server represents a number of bug fixes, including security fixes that depend upon the NSS shared component. For details, see the appropriate release notes.
Web Server Upgrade Roadmap
Table 5-1 shows the supported Web Server upgrade paths to Java ES Release 4.
Compatibility Issues
Release 4 Web Server does not introduce any interface changes and is backwardly compatible with Release 3.
Web Server Dependencies
Web Server has no dependencies on other Java ES components other than on Java ES shared components (see Table 1-6).
Upgrading Web Server from Java ES Release 3This section includes information about upgrading Web Server from Java ES Release 3 to Java ES Release 4. The section covers the following topics:
Introduction
When upgrading Java ES Release 3 Web Server to Release 4, consider the following aspects of the upgrade process:
- General Upgrade Approach. The upgrade is performed by applying patches to the Release 3 version. No re-configuration of Web Server is required in upgrading from Java ES Release 3 Web Server to Release 4.
- Upgrade Dependencies. Web Server has dependencies on a number of Java ES shared components Table 1-6. Before upgrading the Web Server upgrade the following shared Java ES shared components.
- Backward Compatibility. Release 4 Web Server is backwardly compatible with the Release 3 version.
- Upgrade Rollback. Rollback of the Release 4 upgrade to Release 3 is achieved by removing the patches applied during the upgrade.
Web Server Upgrade
This section describes how to perform an upgrade of Web Server from Java ES Release 3 to Java ES Release 4 on HP-UX. The section covers the following topics:
Pre-Upgrade Tasks
Before you upgrade Web Server you should perform the tasks described below.
Verify Current Version Information
You can verify the current version of Web Server by starting the Web Server instance server with the -version option:
# web_svr_base/https-hostName.domainName/start -version
Table 5-2 Web Server Version Verification Outputs
Java ES Release
Web Server Version Number
Release 3
6.1SP4
Release 4
6.1SP5
Upgrade Web Server Dependencies
The Java ES shared components listed in (more...) should be upgraded to Java ES Release 4. Instructions for upgrading Java ES shared components to Release 4, are provided in Chapter 2, "Upgrading Java ES Shared Components".
Back Up Web Server Data
The Web Server upgrade from Release 3 to Release 4 does not modify configuration data. There is no need to back up current data.
Obtain Required Configuration Information and Passwords
No special information about your currently installed version is needed. However you will have to log in as superuser to perform the upgrade.
Upgrading Web Server
This section discusses considerations that impact the upgrade procedure for Web Server followed by a description of the procedure itself.
Upgrade Considerations
The upgrade of Web Server software to Java ES Release 4 takes into account the following considerations:
- Any J2EE components running in an Web Server instance should be shut down before you upgrade that instance.
- All Web Server instances corresponding to the same installed Web 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 4 upgrade patches for HP-UX are shown in the following table:
Upgrade Procedure
The procedure documented below applies to all Web Server instances corresponding to the same installed Web Server image on the computer where the upgrade is taking place.
- Obtain the required patches, based on Table 5-3.
Patches can be downloaded from:
- Log in as superuser.
- Stop all running instances of Web Server and the Administration Server.
# web_svr_base/https-instanceName/stop
# web_svr_base/https-admserv/stop
- If not already done, upgrade the shared components listed on (more...) to Release 4.
- Apply the appropriate Web Server patch in Table 5-3.
swinstall -s <patch_location> -x patch_match_target = true
.
Note
If you have Java1.5.0 installed on your computer, uninstall Java 1.5.0 and clean up the installed directory.
- Install Java1.5.0.01.
- Restart the Web Server instances that were stopped in Step 3.
Verifying the Upgrade
You can verify the upgrade of Web Server to Release 4 by starting the Web Server instance server with the -version option:
# web_svr_base/start -version
See Table 5-2 for output values.
Post-Upgrade Tasks
There are no post-upgrade tasks beyond the steps described in the above Upgrade Procedure.
Rolling Back the Upgrade
This section describes considerations that impact the upgrade rollback procedure for Web Server followed by the procedure itself.
Rollback Considerations
The procedure for rolling back the upgrade to Release 4 of Web Server is pretty much the reverse of the procedure for upgrading to Release 4. The patches are removed.
Rollback Procedure
- Log in as superuser.
- Stop all running instances of Web Server and the Administration Server.
# web_svr_base/https-instancename/stop
# web_svr_base/https-admserv/stop
- Remove the Web Server patch in Table 5-3.
# swremove <patch_ID>
- Remove the shared component patches.
# swremove <patch_ID of Shared Component>
- Restart the Web Server instances that were stopped in Step 2.