About Java ES Upgrades

No single system utility upgrades all Java ES components. Instead, the upgrade of Java ES product components to Release 5 is performed component-by-component, computer-by-computer, using component-specific upgrade procedures documented in this guide.

The upgrade of a component can range from a major upgrade, which might not be compatible with the previous version of the component, to a fully compatible upgrade that simply provides bug fixes. Because of dependencies between Java ES components, the nature of the upgrade can affect whether other components need to be upgraded as well.

Product Component Upgrades

Java ES product component upgrades involve two basic operations that mirror the initial installation and configuration of Java ES product components:

• Installation of software upgrades. Upgrade software enhances or fixes existing software or replaces existing software. Software installation can be achieved through the application of patches to existing software packages, the selective replacement of existing packages, the installation of new packages, or a full reinstallation of component software.

• Reconfiguration. Reconfiguration encompasses any change in configuration data, user data, or dynamic application data needed to support the upgraded software. A change in data can mean additional data, a change in data format, whether in property files or database schema, or a change in data location. Sometimes reconfiguration requires that you perform an explicit procedure and sometimes it takes place automatically without your involvement. In some cases, reconfiguration also requires redeployment of component software to a web container.

In addition, Java ES product component upgrades normally involve pre-upgrade tasks and, in some cases, post-upgrade procedures before the upgrade is operational.

Product Component Upgrade Approaches

The upgrade of each product component involves one of the upgrade approaches described in the following sections:

• Performing a Fresh Install of the Component

• Patching Existing Component Packages

Performing a Fresh Install of the Component

Java ES 5 product components are upgraded by performing a fresh install of the components using the Java ES installer. You should install Release 5 in a parallel path and leave the previous version intact. You can reconfigure the product component by migrating the previous version's configuration data to the new installation, or by performing a new configuration, or by doing a combination of both. For some product components a utility is provided for reconfiguring or migrating configuration data for the component.

Patching Existing Component Packages

Web Proxy Server upgrade is performed by manually patching the existing software packages. For more information, see To Upgrade Web Proxy Server.

Upgrade Approach Used for Each Product Component

The upgrade approach used to upgrade each product component to Release 5 is shown in the following table:

Table 1–3 Java ES Product Component Upgrade Approaches

Component	Upgrade Approach	Reconfiguration
Access Manager	Perform fresh install in a parallel path using Java ES installer	Use amconfig.bat and amupgrade.bat files to reconfigure and redeploy to web container
Application Server	Perform fresh install in a parallel path using Java ES installer	None
Directory Proxy Server	Perform fresh install in a parallel path using Java ES installer	Manual reconfiguration
Directory Server	Perform fresh install in a parallel path using Java ES installer	Use dsmig command to migrate Directory Server data
Message Queue	Perform fresh install in a parallel path using Java ES installer	None
Service Registry	Perform fresh install in a parallel path using Java ES installer	Manual reconfiguration
Web Proxy Server	Patch binaries	None
Web Server	Perform fresh install in a parallel path using Java ES installer	Use wadm migrate-server command to migrate server instance configuration

Shared Component Upgrades

Java ES shared component upgrades are a necessary part of upgrading the product component that depend on them. Shared components for Release 5 need to be installed using the Release 5 installer in a parallel path. Release 5 installer does not upgrade Release 4 shared components.