Chapter 6 Web Server

This chapter describes how to upgrade Web Server to Java ES 2005Q4 (Release 4): Sun Java System Web Server 6.1 SP5 2005Q4.

The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Java ES Release 4. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Web Server Upgrades

Upgrading Web Server from Java ES Release 3

Upgrading Web Server from Java ES Release 2



Note	File locations in this chapter are specified with respect to a directory path referred to as WebServer-base. At least part of this path might have been specified as an installation directory when Web Server was initially installed. If not, the Java ES installer assigned a default value. The default value of WebServer-base depends on operating system platform: Solaris: /opt/SUNWwbsvr Linux: /opt/sun/webserver

Overview of Web Server Upgrades

This section describes the following general aspects of Web Server that impact upgrading to Java ES 2005Q4 (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.

Web Server Upgrade Roadmap

Table 6-1 shows the supported Web Server upgrade paths to Java ES Release 4. The table applies to both Solaris and Linux operating systems.

Table 6-1 Upgrade Paths to Java ES Release 4: Sun java System Web Server 6.1 SP5 2005Q4
Java ES Release	Web Server Version	General Approach	Re-configuration Required
Release 3	Sun Java System Web Server 6 2005Q1 Update 1 SP 4	Direct upgrade: Performed by applying patches.	None
Release 2	Sun Java System Web Server 6 2004Q2 Update 1 SP 2 Platform and Enterprise Editions	Direct upgrade: Performed by applying patches.	None
Release 1	Sun ONE Web Server 6.1 (2003Q4)	Direct upgrade not certified: But can be performed by applying patches.	None
Pre-dates Java ES releases		No direct upgrade.

Web Server Data

The following table shows the type of data that could be impacted by an upgrade of Web Server software.

Table 6-2 Web Server Data Usage
Type of Data	Location	Usage
Configuration data	WebServer-base/https-instanceName/config/obj.conf and other files in the same directory	Configuration of Web Server instance

Compatibility Issues

Java ES Release 4 Web Server does not introduce any interface changes and is backwardly compatible with earlier versions.

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 3

This section includes information about upgrading Web Server from Java ES 2005Q1 (Release 3) to Java ES 2005Q4 (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. While Web Server has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Web Server requires only that NSS and NSPR be upgraded to Release 4. Upgrade of other shared components is optional with respect to upgrade of Web Server to Release 4.

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.

Platform Issues. The general approach for upgrading Web Server is the same on both Solaris and Linux operating systems, however the patching technologies are different. The upgrade process therefore includes platform-specific procedures.

Release 3 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 both the Solaris and Linux platform. Where a topic depends on platform-specific procedures, the topic will indicate the operating system to which it applies. The section covers the following topics:

Pre-Upgrade Tasks

Verify Current Version Information

You can verify the current version of Web Server by starting the Web Server instance server with the -version option:

WebServer-base/https-hostName.domainName/start -version

Table 6-3 Web Server Version Verification Outputs
Java ES Release	Web Server Version Number
Release 2	6.1SP2
Release 3	6.1SP4
Release 4	6.1SP5

Upgrade Web Server Dependencies

It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Java ES Release 4. However, the upgrade of Web Server to Release 4 requires only that the NSS and NSPR shared component be upgraded from Release 3 to its Release 4 version before upgrading Web Server. Instructions for upgrading NSS and NSPR to Release 4, or other Java ES shared components you might wish to upgrade, 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 Release 3 Web Server (Solaris)

This section discusses considerations that impact the upgrade procedure for Web Server followed by a description of the procedure itself.

Upgrade Considerations (Solaris)

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 Web Server upgrade patches for Solaris OS are shown in the following table:

Table 6-4 Patches1 to Upgrade Web Server on Solaris
Description	SPARC Solaris 8, 9, & 10	X86 Solaris 9 & 10
Web Server core (SUNWwbsvr)	116648-17	116649-17
Web Server localization	117514-10	117515-10

1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table.

Upgrade Procedure (Solaris)

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 6-4.

Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

su -

Stop all running instances of Web Server and the Administration Server.

WebServer-base/https-instanceName/stop
WebServer-base/https-admserv/stop

If you have not already done so, upgrade the NSS and NSPR shared component to Release 4 and any other shared components you wish to upgrade.

See Upgrade Web Server Dependencies.

Apply the appropriate Web Server patches in Table 6-4.

patchadd patch_ID

Confirm that the patch upgrade was successful:

showrev -p | grep patch_ID

The output should return the versions of patch IDs applied in Step 5.

Restart the Web Server instances that were stopped in Step 3.

Upgrading Release 3 Web Server (Linux)

This section discusses considerations that impact the upgrade procedure for Web Server followed by a description of the procedure itself.

Upgrade Considerations (Linux)

The upgrade of Web Server software to Java ES Release 4 on the Linux platform takes into account the same considerations as on the Solaris platform (see Upgrade Considerations (Solaris)), except that the Linux Release 4 upgrade patches differ from the Solaris patches.

The Release 4 Web Server upgrade patches for Linux OS are shown in the following table:

Table 6-5 Patches1 to Upgrade Web Server on Linux
Description	Patch ID and RPM names
Web Server core	118202-09 sun-webserver-6.1.5-6.i386.rpm
Web Server localization	118203-06 sun-webserver-Locale-6.1.5-1.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Java ES Release 4. If newer revisions become available, use the newer ones instead of those shown in the table

Upgrade Procedure (Linux)

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.


Caution	An upgrade from Java ES Release 3 to Java ES Release 4 on Linux cannot be rolled back.

Obtain the required patches using the patch numbers and RPM names from Table 6-5. Use this information to obtain the version numbers for the RPM.

Patches can be downloaded to /tmp from: http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access

su -

Stop all running instances of Web Server and the Administration Server.

WebServer-base/https-instanceName/stop
WebServer-base/https-admserv/stop

If you have not already done so, upgrade the NSS and NSPR shared component to Release 4 and any other shared components you wish to upgrade.

See Upgrade Web Server Dependencies.

Apply the RPMs for Web Server in Table 6-5.

rpm -Fvh sun-webserver-6.1.5-6.i386.rpm

Confirm that the upgrade was successful:

rpm -q sun-webserver

The new revision number of the RPM should be returned.

Restart the Web Server instances that were stopped in Step 3.

WebServer-base/https-admserv/start
WebServer-base/https-instanceName/start

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:

Post-Upgrade Tasks

Rolling Back the Upgrade (Solaris)

This section describes considerations that impact the upgrade rollback procedure for Web Server followed by the procedure itself.

Rollback Considerations (Solaris)

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 (Solaris)

su -

Stop all running instances of Web Server and the Administration Server.

WebServer-base/https-instancename/stop
WebServer-base/https-admserv/stop

Remove the patches in Table 6-4.

patchrm patch_ID

Restart the Web Server instances that were stopped in Step 2.

Upgrading Web Server from Java ES Release 2

The procedure for upgrading Java ES 2004Q2 (Release 2) Web Server to Release 4 is the same as that for upgrading Release 3 Web Server to Release 4, with the exception that the pre-upgrade tasks should include the upgrading of all shared components upon which Web Server depends (see Table 1-6) from their Release 2 versions to Release 4.

To upgrade Release 2 Web Server to Release 4, use the instructions in Upgrading Web Server from Java ES Release 3, except substitute Release 2 wherever Release 3 is referenced. The upgrade from Release 2 to Release 4, however, also requires modification of the obj.conf configuration file, but this is performed automatically.

Previous Contents Index Next
Sun Java Enterprise System 2005Q4 Upgrade Guide