Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java Enterprise System 5 Update 1 Upgrade Guide for UNIX 

Chapter 13
Web Proxy Server

This chapter describes how to upgrade Web Proxy Server to Java ES 5 Update 1 (Release 5U1): Sun Java System Web Proxy Server 4.0.5. It covers both feature upgrades from previous Java ES release families and maintenance upgrades from Java ES 5.

The chapter provides an overview of upgrade considerations for the different upgrade paths supported by Release 5U1. The chapter covers upgrades on both the Solaris and Linux operating systems:

Overview of Web Proxy Server Upgrades

This section describes the following general aspects of Web Proxy Server that impact upgrading to Java ES 5 Update 1 (Release 5U1):

About Release 5U1 Web Proxy Server

Release 5U1 Web Proxy Server is a maintenance release that fixes bugs in Release 5 Web Proxy Server. Release 5 Web Proxy Server, in turn, was a bug-fix release with respect to Release 4.

However, Release 5 Web Proxy Server includes better performance, more scalable architecture, better standards compliance, and a new administration interface as compared to Sun One Web Proxy Server 3.6, that is, before the inclusion of Web Proxy Server in Java Enterprise System.

Web Proxy Server Upgrade Roadmap

Table 13-2 shows the Web Proxy Server upgrade path to Release 5U1. The table applies to the Solaris OS only, because Web Proxy Server was not previously supported on the Linux OS.

Table 13-2 Upgrade Paths to Java ES 5 Update 1 (Release 5U1): Web Proxy Server 4.0.5

Java ES Release

Web Proxy Server Version

General Approach

Reconfiguration Required

Release 5

Sun Java System Web Proxy Server 4.0.4

Maintenance upgrade. Apply patches.

None

Release 4

Sun Java System Web Proxy Server 4.0.1 2005Q4

Maintenance upgrade. Apply patches.

None

Pre-dates Java ES releases
(Solaris OS only)

Sun ONE Web Proxy Server 3.6

(Hereafter referred to as Version 3.6)

Feature upgrade. Direct upgrade performed using the Java ES installer to install in new location then migrating configuration data using administration tools

Configuration information must be migrated to new location.

Web Proxy Server Data

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

Table 13-3 Web Proxy Server Data Usage

Type of Data

Location

Usage

Configuration data

WebProxyServer-base/proxy-serverid/
config directory

Contains files such as: server,xml, magnus.conf, obj.conf, and so forth

Stores configuration information for the server, cache, filters, routing, and other functional aspects of Web Proxy Server

Web Proxy Server Upgrade Strategy

Your strategy for upgrading Web Proxy Server generally depends on the many considerations discussed in Chapter 1, "Planning for Upgrades": upgrade path, dependencies between Java ES components, selective upgrade versus upgrade all, multi-instance deployments, and so forth.

This section is to particularize that general discussion to Web Proxy Server by presenting issues that might influence your Web Proxy Server upgrade plan.

Compatibility Issues

Release 5U1 Web Proxy Server does not introduce any new public interfaces and is backwardly compatible with Release 4 and Release 5 Web Proxy Server. Release 5U1 Web Proxy Server is also compatible with Version 3.6, except that plug-ins developed using the NSAPI interface supported by Version 3.6 must be recompiled with the NSAPI interface supported by Release 5U1.

Web Proxy Server Dependencies

Web Proxy Server has dependencies on the following Java ES components:

Dual Upgrade

Dual upgrades, in which both Web Proxy Server and operating system are upgraded (as described in Dual Upgrades: Java ES and Operating System Software) can be performed using the in-place operating system upgrade approach:

  1. Back up existing Web Proxy Server data.

    2. See Web Proxy Server Data for the location of essential data.

  2. Upgrade the operating system.

    3. The upgrade leaves the existing file system in place.

  3. Upgrade to Release 5U1 Web Proxy Server.

    4. See the appropriate section of this chapter, depending on upgrade path.

Upgrading Web Proxy Server from Release 5

This section includes information about upgrading Web Proxy Server from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

When upgrading Release 5 Web Proxy Server to Release 5U1, consider the following aspects of the upgrade process:

Release 5 Web Proxy Server Upgrade

This section provides an overview of how to perform an upgrade of Web Proxy Server to Release 5U1. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Web Proxy Server, you should perform the following tasks:

Verify Current Version Information

You can verify the current version of Web Proxy Server by entering the following command:

Upgrade Web Proxy Server Dependencies

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 the NSS and NSPR shared components be upgraded. If these shared components have not yet been upgraded, you should upgrade them to Release 5U1 before upgrading Web Proxy Server. Instructions are provided in Chapter 2, "Upgrading Java ES Shared Components".

Back Up Web Proxy Server Data

The Web Proxy Server upgrade to Release 5U1 does not modify Release 5 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 5 Web Proxy Server (Solaris)

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

Upgrade Considerations (Solaris)

The upgrade of Web Proxy Server software to Release 5U1 takes into account the following considerations:

Upgrade Procedure (Solaris)

The procedure documented below applies to Web Proxy Server on the computer where the upgrade is taking place.

  1. Log in as root or become superuser.

    2. su -

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

    3. WebProxyServer-base/proxy-instanceName/stop
    WebProxyServer-base/proxy-admserv/stop

  3. If you have not already done so, synchronize all shared component to Release 5U1.

    4. Instructions are provided in Chapter 2, "Upgrading Java ES Shared Components".

  4. Obtain the latest Web Server upgrade patches, based on Table 13-5.

    5. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  5. Apply the appropriate Web Proxy Server core and, if needed, localization patches in Table 13-5, in that order.

    6. patchadd /workingDirectory/patch_ID

    Be sure to consult the README.patch_ID file for additional patch installation instructions.

  6. Confirm that the patch upgrades were successful:

    7. showrev -p | grep patch_ID

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

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

    8. WebProxyServer-base/proxy-admserv/start
    WebProxyServer-base/proxy-instanceName/start

Upgrading Release 5 Web Proxy Server (Linux)

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

Upgrade Considerations (Linux)

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

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

Table 13-6 Patches1 to Upgrade Web Proxy Server on Linux 

Description

Patch ID and RPM names

Web Proxy Server core

120983-12

  • sun-proxyserver-4.0.6-12.i386.rpm

Web Proxy Server localization

126329-01

  • sun-proxyserver-l10n-4.0.5-1.i386.rpm

1Patch revision numbers are the minimum required for upgrade to Java ES Release 5U1. 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 Web Proxy Server on the computer where the upgrade is taking place.

Caution

An upgrade from Release 5 to Release 5U1 on Linux cannot be rolled back.

  1. Log in as root or become superuser.

    2. su -

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

    3. WebProxyServer-base/proxy-instanceName/stop
    WebProxyServer-base/proxy-admserv/stop

  3. If you have not already done so, synchronize all shared component to Release 5U1.

    4. See Upgrade Web Proxy Server Dependencies.

  4. Obtain the latest Web Proxy Server upgrade patches, based on Table 13-6.

    5. To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to /workingDirectory.

  5. Apply the core and, if needed, localization RPMs for Web Proxy Server in Table 13-6, in that order.

    6. rpm -Fvh *.rpm

    Be sure to consult the README.patch_ID file for additional patch installation instructions.

  6. Confirm that the patch upgrades were successful:

    7. rpm -qa | grep sun-proxyserver

    The new version numbers of the RPMs should be returned.

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

    8. WebProxyServer-base/proxy-admserv/start
    WebProxyServer-base/proxy-instanceName/start

Verifying the Upgrade

You can verify the upgrade of Web Proxy Server to Release 5U1 by starting a Web Proxy Server instance with the -version option:

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure (Solaris) and Upgrade Procedure (Linux).

Rolling Back the Upgrade (Solaris)

The procedure for rolling back the upgrade to Release 5U1 of Web Proxy Server is pretty much the reverse of the procedure for upgrading to Release 5U1.

  1. Log in as root or become superuser.

    2. su -

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

    3. WebProxyServer-base/proxy-instanceName/stop
    WebProxyServer-base/proxy-admserv/stop

  3. Remove the patches in Table 13-5.

    4. patchrm patch_ID

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

    5. WebProxyServer-base/proxy-admserv/start
    WebProxyServer-base/proxy-instanceName/start

Rolling Back the Upgrade (Linux)

This section describes the Release 5U1 upgrade rollback procedure for Web Proxy Server on the Linux platform. There is no automated rollback procedure for Linux patches, so the recommended approach is to manually overwrite the Release 5U1 RPMs with the Release 5 RPMs, as described below.

  1. Log in as root or become superuser.

    2. su -

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

    3. WebProxyServer-base/proxy-instanceName/stop
    WebProxyServer-base/proxy-admserv/stop

  3. Check the revision numbers of Web Proxy Server RPMs.

    4. rpm -qa | grep sun-proxyserver

    The updated RPMs should be those listed in Table 13-6.

  4. Check to see if the RPMs have been relocated from their default location.

    5. rpm -q --queryformat '%{INSTALLPREFIX}' rpmName

    where rpmName is the unique name of the RPM (for example, the values sun-proxyserver-* shown in Table 13-6). The command returns a prefixValue as a path to the installed RPM.

  5. Reinstall Release 5 RPMs from the Java ES 5 distribution.

    6. (If you are rolling back to a post-Release 5 sustaining patch, rather than to Release 5, reinstall the RPMs from that patch.)

    rpm -Uvh --force [--prefix prefixValue] *.rpm

    The --force option will allow the command to overwrite later packages of the same name. The --prefix option is not required unless the RPMs have been relocated. (If only a subset of the RPMs had been relocated, use individual file names as command arguments rather than *.rpm.)

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

    7. WebProxyServer-base/proxy-admserv/start
    WebProxyServer-base/proxy-instanceName/start

Upgrading Web Proxy Server from Java ES Release 4

The procedure for upgrading Java ES 2005Q4 (Release 4) Web Proxy Server to Release 5U1 is the same as that for upgrading Release 5 Web Proxy Server to Release 5U1.

To upgrade Release 4 Web Proxy Server to Release 5U1, use the instructions in Upgrading Web Proxy Server from Release 5, except substitute Release 4 wherever Release 5 is referenced and substitute the following patches:

Table 13-7 Patches1 to Upgrade Web Proxy Server on Solaris 

Description

Patch ID: SPARC

Solaris 9 & 10

Patch ID: X86

Solaris 9 & 10

Web Proxy Server core

120981-11

120982-11

Web Proxy Server localization

122963-02

122964-02

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

Table 13-8 Patches1 to Upgrade Web Proxy Server on Linux 

Description

Patch ID and RPM names

Web Proxy Server core

120983-11

  • sun-proxyserver-4.0.5-1.i386.rpm

Web Proxy Server localization

122965-02

  • sun-proxyserver-Locale-4.0.5-1.i386.rpm

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

Upgrading Web Proxy Server from Version 3.6

This section includes information about upgrading Web Proxy Server from Version 3.6 to Java ES 5 Update 1 (Release 5U1). The section covers the following topics:

Introduction

When upgrading Version 3.6 Web Proxy Server to Release 5U1, consider the following aspects of the upgrade process:

Version 3.6 Web Proxy Server Upgrade

This section provides an overview of how to perform an upgrade of Web Proxy Server to Release 5U1. Web Proxy Server was not previously supported on the Linux platform. Hence upgrade of Web Proxy Server to Release 5U1 is only performed on the Solaris platform. The section covers the following topics:

Pre-Upgrade Tasks

Before you upgrade Web Proxy Server, you should perform the following tasks:

Verify Current Version Information

You can verify the current version of Web Proxy Server by entering the following command:

Upgrade Web Proxy Server Dependencies

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 Java ES installer that is used to upgrade Web Proxy Server to Release 5U1 automatically upgrades all shared components upon which Web Proxy Server depends (see Table 1-10).

Back Up Web Proxy Server Data

The Web Proxy Server upgrade to Release 5U1 does not modify Version 3.6 configuration data. However any unsaved changes to Version 3.6 configuration data made using the administration interface must be saved before performing the upgrade.

Obtain Required Configuration Information and Passwords

To upgrade from Version 3.6, you need to know the installation directory path for that installed version.

Upgrading Version 3.6 Web Proxy Server

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

Upgrade Considerations

All Web Proxy Server instances corresponding to the same installed Web Proxy Server image can be upgraded. However, the migration of configuration data has to be done separately for each instance. All such instances should be shut down when migration is performed to make sure that no port conflicts arise when migrated instance is started.

Upgrade Procedure

The procedure documented below applies to Web Proxy Server software on the computer where the upgrade is taking place.

  1. Log in as root or become superuser.

    2. su -

  2. Install Web Proxy Server Release 5U1.
    1. Run the Java ES installer from the Java ES 5 Update 1 distribution.
    2. Select Web Proxy Server from the component selection page.
    3. Select the Configure Now option.
    4. Quit the Java ES installer when installation is complete.
  3. Apply the latest Web Proxy Server maintenance patches, if any.
    1. Check if there have been any Web Proxy Server point fixes subsequent to Release 5U1.

      2. Periodically obtain the latest patches as described in Accessing Java ES Patches and compare them to the Release 5U1 patch revision numbers shown in Table 13-5 (Solaris) or Table 13-6 (Linux).

      If you are using Sun Connection on the Solaris platform, you are automatically notified of new patches for Java ES components installed on your computer.

    2. Apply the appropriate Web Proxy Server core and, if needed, localization patches in that order.

      3. On Solaris:
      patchadd /workingDirectory/patch_ID

      If you are using the accumulated patch cluster on the Solaris platform, the install_cluster script will apply any Java ES patches needed on your computer.

      On Linux:
      rpm -Fvh *.rpm

      Be sure to consult the README.patch_ID file for additional patch installation instructions.

    3. Confirm that the patch upgrades were successful:

      4. On Solaris:
      showrev -p | grep patch_ID

      On Linux:
      rpm -qa | grep sun-proxyserver

      The output should return the appropriate patch IDs or version numbers.

  4. Migrate configuration settings to the newly installed version.

    5. This operation must be performed separately for each Web Proxy Server instance.

    1. Start the Web Proxy Server Administration Server.

      2. WebProxyServer-base/proxy-admserv/start

    2. Log in to the administration graphical interface.
    3. Click on the Server tab and then click Migrate Server.
    4. Specify the Version 3.6 installation directory path.
    5. Select the instance to migrate.
    6. Click the Migrate button.

      7. After successful migration, the migration screen provides a list of additional configurations that must be performed manually. It provides the data that needs to be added and the corresponding configuration file.

      For more information on migrating configuration settings refer to Sun Java System Web Proxy Server 4.0.4 Installation and Migration Guide, http://docs.sun.com/doc/819-5492.

  5. Make any additional configuration changes specified in Step f.

    6. Refer to the Sun Java System Web Proxy Server 4.0.4 Configuration File Reference, http://docs.sun.com/doc/819-5494, for more information.

Verifying the Upgrade

You can verify the upgrade of Web Proxy Server to Release 5U1 by starting a Web Proxy Server instance with the -version option:

See Table 13-9 for output values.

Post-Upgrade Tasks

There are no post-upgrade tasks beyond the steps described in Upgrade Procedure.

Rolling Back the Version 3.6 Upgrade

The upgrade of Web Proxy Server to Release 5U1, documented in Upgrading Version 3.6 Web Proxy Server, cannot be rolled back. However, you can revert to Version 3.6, which was left intact by the Release 5U1 upgrade procedure.



Previous      Contents      Index      Next     

Part No: 820-2510-10
November 2007.   Copyright 2004 Sun Microsystems, Inc. All rights reserved.