This chapter describes how to upgrade Application Server from Java ES 5 (Release 5) to Java ES 5 Update 1 (Release 5U1): Sun Java System Application Server Enterprise Edition 8.2 Patch2.
The chapter provides a general overview of upgrade issues and procedures for the different upgrade paths supported by Release 5U1. The chapter covers the following topics:
File locations in this chapter are specified with respect to a directory path referred to as ApplicationServer-base. At least part of this path might have been specified as an installation directory when Application Server was initially installed. If not, the Java ES installer assigned a default value.
The default value of ApplicationServer-base is C:\Program Files\Sun\JavaES5\appserver
The following sections describe general aspects of Application Server that affect upgrading to Java ES 5 Update 1:
Release 5U1 Application Server is a maintenance release that fixes bugs in Release 5 Application Server. Release 5 Application Server (Application Server 8.2) was a maintenance release with respect to Release 4 (Application Server 8.1 UR2), including only selected bug fixes. Release 5U1 Application Server is functionally the same as Release 4.
The following table shows the supported Application Server upgrade paths to Java ES 5 Update 1.
Table 9–1 Upgrade Paths to Java ES 5 Update 1: Sun Java System Application Server Enterprise Edition 8.2 Patch2
Java ES Release |
Application Server Release |
General Approach |
Reconfiguration Required |
---|---|---|---|
Release 5 |
Sun Java System Application Server Enterprise Edition 8.2 |
Maintenance Upgrade. Apply patches. |
None |
Release 4 |
Direct upgrade of Application Server from Release 4 to Release 5U1 is not supported. This upgrade path is supported by first upgrading Release 4 Application Server to Release 5 Application Server and then upgrading Release 5 to Release 5U1. The information about upgrading Release 4 to Release 5 is documented in Sun Java ES 5 Upgrade Guide for Microsoft Windows. |
The following table shows the type of data that could be affected by an upgrade of Application Server software.
Table 9–2 Application Server Data Usage
Type of Data |
Location |
Usage |
---|---|---|
Environment variables |
ApplicationServer-base\config\asenv.bat |
Global variables |
Configuration data |
ApplicationServer-base\domains\domainName\config |
Configuration of Application Server instances |
Deployment data |
ApplicationServer-base\domains\domainName\applications |
Configuration of J2EE container for specific J2EE components and applications |
Java ES 5 Update 1 Application Server does not introduce any interface changes with respect to Java ES 5.
Application Server dependencies on other Java ES components can affect the procedure for upgrading and reconfiguring Application Server software. Changes in Application Server interfaces or functions, for example, could require upgraded versions of components upon which Application Server depends. The need to upgrade such components depends upon the specific upgrade path.
Application Server has dependencies on the following Java ES components:
Shared components. Application Server has dependencies on specific Java ES shared components, as listed in Table 1–8.
Message Queue. Application Server depends on Message Queue to provide J2EE Java Message Service-compliant asynchronous messaging support.
HADB. Application Server depends on High Availability Database (HADB) for high availability storage of HTTP session. HADB is designed to support up to 99.999% service and data availability with load balancing, failover, and state recovery.
NSS. Application Server depends on Network Security Service (NSS) for managing security.
Web Container (optional). Application Server depends upon web container services for its optional load balancing plug-in. This support can be provided by Java ES Web Server.
This section includes information about upgrading Application Server from Java ES 5 to Java ES 5 Update 1 . The section covers the following topics:
When upgrading Release 5 Application Server to Release 5U1, consider the following aspects of the upgrade process:
General Upgrade Approach. The upgrade is achieved by patching Release 5 Application Server.
Upgrade Dependencies. Application Server has dependencies on a number of Java ES shared components (see Table 1–8).
Backward Compatibility. Release 5UI Application Server is backwardly compatible with the Release 5 version.
This section describes how to perform an upgrade of Application Server from Java ES Release 5 to Release 5U1. This section covers the following topics:
Before you upgrade Application Server, perform the tasks described below.
Verify the current version of Application Server before you upgrade.
Type the following command:
WebServer-base\asadmin version --verbose
This command returns the Application Server version information.
Sun Java Enterprise System Application Server Enterprise Edition 8.2
Sun Java Enterprise System Application Server Enterprise Edition 8.2
It is generally recommended that all Java ES components on a computer system (and in a computing environment) be upgraded to Release 5U1. Release 5U1 Application Server has hard upgrade dependencies on Message Queue and on the NSS shared component, so these should be upgraded before upgrading Application Server. Upgrading Application Server to Release 5U1 requires that Windows Installer patch (126910–02) is already applied.
The Application Server upgrade from Release 5 to Release 5U1 does not modify the Release 5 configuration data. You do not need to back up current data.
This section discusses considerations that impact the upgrade procedure for Application Server, followed by a description of the procedure itself.
The upgrade of Application Server software to Java ES Release 5U1 takes into account the following considerations:
In a deployment architecture in which there are multiple instances of Application Server running on a single computer (all corresponding to the same installed Application Server image), you only have to upgrade the Application Server image once.
In a maintenance upgrade, you do not have to migrate schema, configuration, security or user data.
The Release 5U1 Application Server upgrade patches for Windows are shown in the following table:
The procedure documented below applies to Application Server instances residing locally on the computer where the upgrade is taking place.
Log in as administrator.
Shut down all Application Server instances.
Make sure you have upgraded any Java ES components upon which Application Server has hard upgrade dependencies (see Upgrade Web Server Dependencies.
Obtain the required Application Server Release 5U1 upgrade patches, based on Table 9–3.
To obtain the patch, see Accessing Java ES Patches. Patches can be downloaded to \workingDirectory.
Install the patch.
Installation is generally performed by running patch-id.exe, however, be sure to consult the README.patch-id file in the patch directory for installation instructions.
If you are prompted to restart the system, select No. Wait till the patch installation process is completed and then restart and re-login as the same user to complete the patch installation.
Verify the patch log file.
The log file is found at: %TEMP%\SUNJAVAES_<patch-id>.log
Verify the patch installation with the utility ListJavaESPatches.exe.
Run ListJavaESPatches.exe and check that the output includes the patch id of the patch that you have installed in Step 5. For more information, see Identifying Installed Java ES Patches.
Start the Release 5U1 Application Server domains and node-agents of all the instances.
ApplicationServer-base\bin\asadmin.bat start-domain --user admin-user-ID/ --passwordfile passwordFileName domain-name
ApplicationServer-base\bin\asadmin.bat start-node-agent --port admin-Port --user/ admin-user-ID --password admin-password node-agent--name
You can verify successful upgrade of Application Server by starting the Application Server instance as follows:
AppServer-base\bin\asadmin version --verbose
The messages that indicate the Java ES release version are:
Sun Java Enterprise System Application Server 8.2 (build b30–p02)
Sun Java Enterprise System Application Server 8.2 (build b25–fcs)
The upgrade will not update version numbers.
To update the version string, do the following:
Copy unzipped installable binary\scripts\PostPatch.class to ApplicationServer-base\lib
Execute java PostPatch from the directory ApplicationServer-base\lib.
Log in as administrator.
Shut down the Application Server instances.
Double-click Uninstall_patch-id.bat to uninstall the patch.
Execute java PostPatch from the directory ApplicationServer-base\lib.
Restart the administration server and the Application Server instances that were shut down in step 2.