Sun Java Enterprise System 5 Update 1 Upgrade Guide for Microsoft Windows

Upgrade Sequencing Guidelines

The following listing provides the order in which Java ES components can be successfully upgraded on a single computer or in a deployed system. When you plan your upgrade, you can omit those components that are not part of your deployment architecture.

The chapters in this guide are arranged according to the order in which components appear in the following listing.

Note –

Before applying Java ES 5 Update 1 patches, be sure that the following Java ES Windows Installer patch has been installed:

126910–02 [Revision number indicated for the Java ES Windows Installer patch is the minimum required for upgrade to Release 5U1. If newer revision becomes available, use the newer one.]

  1. Shared Components ( Chapter 2, Upgrading Java ES Shared Components)

    Shared components should be upgraded before the components which depend on them.

  2. Directory Server (Chapter 3, Directory Server)

    Many components store user data or configuration data in Directory Server, so upgrades to Directory Server should generally be performed before upgrading the components that have runtime or configuration dependencies on Directory Server.

  3. Directory Proxy Server (Chapter 4, Directory Proxy Server)

    Directory Proxy Server has a soft upgrade dependency on Directory Server and can be upgraded at any time. Some components might access Directory Server through Directory Proxy Server, however, so if Directory Proxy Server is upgraded, it should be upgraded right after Directory Server.

  4. Web Server (Chapter 5, Web Server)

    A number of Java ES components require the support of a web container, which, if upgraded, should be upgraded before the components requiring web container services. Normally web container services are provided by Web Server or Application Server, but if your architecture contains both, upgrade Web Server first, before upgrading Application Server.

  5. Java DB (Chapter 6, Java DB)

    Java DB must be upgraded before Application Server, which requires Java DB as a default database.

  6. High Availability Session Store (Chapter 7, High Availability Session Store)

    Upgrade is not supported for High Availability Session Store to Java ES 5 U1 (Release 5U1) on Windows.

  7. Message Queue (Chapter 8, Message Queue)

    Message Queue must be upgraded before Application Server, which requires Message Queue to be Java 2 Enterprise Edition (J2EE) compliant.

  8. Application Server (Chapter 9, Application Server)

    Application Server depends on Web Server for its load balancing plug in, so if you are using that capability, Application Server should be upgraded after Web Server.

  9. Service Registry (Chapter 10, Service Registry)

    Service Registry can be upgraded any time after Application Server is upgraded because it depends upon Application Server for runtime container services.

  10. Web Proxy Server (Chapter 11, Web Proxy Server)

    Web Proxy Server can be upgraded any time, though generally it would be upgraded after the Web Server or Application Server component for which it provides a proxy service. Web Proxy Server is a new Java ES Release 5U1 component that can be upgraded from its previous non-Java ES release.

  11. Access Manager (Chapter 12, Access Manager)

    Upgrade is not supported for Access Manager to Java ES 5 U1 (Release 5U1) on Windows.

  12. Monitoring Console (Chapter 13, Monitoring Console)

    Monitoring Console has dependencies on a number of Java ES shared components (see Table 1–8), two of which are hard upgrade dependencies and need to be upgraded when you perform a maintenance upgrade of MFWK and SJWC.

  13. Portal Server (Chapter 14, Portal Server)

    Upgrade is not supported for Sun Java System Portal Server 7.1 to Java ES 5 U1 (Release 5U1) on Windows.