Chapter 9 Application Server

This chapter describes how to upgrade Application Server to Java ES 2005Q4 (Release 4): Sun Java System Application Server Enterprise Edition 8.1 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 Application Server Upgrades

Upgrading Application Server from Java ES Release 3

Upgrading Application Server from Java ES Release 2



Note	File locations in this chapter are specified with respect to directory paths referred to as AppServer8-base and AppServer8Config-base (Application Server 8.1), AppServer7-base and AppServer7Config-base (Application Server 7). At least part of these paths might have been specified as installation directories when Application Server was installed. If not, the Java ES installer assigned a default value. The default values of these directory paths are shown in the following table.


Path Name	Solaris OS	Linux OS
AppServer8-base	/opt/SUNWappserver/appserver	/opt/sun/appserver
AppServer8Config-base	/var/opt/SUNWappserver	/var/opt/sun/appserver
AppServer7-base	/opt/SUNWappserver7	/opt/SUNWappserver7
AppServer7Config-base	/var/opt/SUNWappserver7	/var/opt/SUNWappserver7

Overview of Application Server Upgrades

This section describes the following general aspects of Application Server that impact upgrading to Java ES 2005Q4 (Release 4):

About Java ES Release 4 Application Server

Java ES Release 4 Application Server represents selected bug fixes to the Release 3 version. Functionally Release 4 Application Server is the same as Release 3.

Application Server Upgrade Roadmap

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

Table 9-1 Upgrade Paths to Java ES Release 4: Sun Java System Application Server
Enterprise Edition 8.1 2005Q4
Java ES Release	Application Server Version	General Approach	Re-configuration Required
Release 3	Sun Java System Application Server Enterprise Edition 8.1 2005Q1	Direct upgrade: Performed by applying patches.	None
Release 2	Sun Java System Application Server 7.0 Upgrade 3 (2004Q2) Platform and Enterprise Editions	Direct upgrade: Use the Java ES installer then the re-configuration utility.	Environment variables and other configuration data. J2EE components and applications need to be migrated to new Application Server environment and redeployed.
Release 1	Sun ONE Application Server 7.0 Upgrade 1 (2003Q4) Platform and Enterprise Editions	Direct upgrade not certified: But you can use the Java ES installer then the re-configuration utility.	Environment variables and other configuration data. J2EE components and applications need to be migrated to new Application Server environment and redeployed.
Pre-dates Java ES releases		No direct upgrade: But you can upgrade first to Release 3 using procedures in the Java Enterprise System 2005Q1 Upgrade and Migration Guide (http://docs.sun.com/doc/819-0062). Then upgrade from Release 3 to Release 4.

In addition to the Java ES releases of Application Server shown in Table 9-1, Application Server Platform Edition is also bundled with Solaris operating system software. Upgrade of the bundled versions of Application Server to Release 4 Enterprise Edition can be performed by the Java ES installer. You simply select Application Server for installation by the installer, as in a new install, and the installer software will automatically upgrade the bundled version, performing any re-configuration of Application Server that might be necessary.

Application Server Data

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

Table 9-2 Application Server Data Usage
Type of Data	Location	Usage
Environment variables	AppServer8-base/config/asenv	Global variables
Configuration data	Release 3 & Release 4: domain.xml and server.policy files in AppServer8Config-base/domains/domainName/config Release 2: server.xml and server.policy files in AppServer7Config-base/domains/domainName/ instanceName/config	Configuration of Application Server instances
Deployment data	Release 3 & Release 4: AppServer8Config-base/domains/domainName/ applications Release 2: AppServer7Config-base/domains/domainName/ instanceName/applications	Configuration of J2EE container for specific J2EE components and applications.

Compatibility Issues

Release 4 Application Server does not introduce any interface changes with respect to Release 3. However, there are major interface changes between Release 4 and Release 2, making Release 4 incompatible with Release 2.

Application Server Dependencies

Application Server dependencies on other Java ES components can impact the procedure for upgrading and re-configuring 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.

Shared components. Application Server has dependencies on specific Java ES shared components (see Table 1-6).

Message Queue. Application Server depends on Message Queue to provide J2EE Java Message Service-compliant asynchronous messaging support.

Web Container (optional). Application Server depends upon web container services for its optional load balancing plugin. This support can be provided either by Java ES Web Server or third-party web containers (such as Apache Web Server, and Microsoft IIS).

High Availability Session Store (optional). Application Server depends upon High Availability Session Store to maintain session state information needed to support failover between instances.

Upgrading Application Server from Java ES Release 3

This section includes information about upgrading Application 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 Application 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 or migration of J2EE components is required to upgrade from Release 3 Application Server to Release 4.

Upgrade Dependencies. While Application Server has dependencies on a number of Java ES shared components (see Table 1-6), Release 4 Application Server is compatible with the Release 3 versions of all these components. Upgrade of these shared components is therefore optional with respect to upgrade of Application Server to Release 4.

In addition, Release 4 Application Server is dependent upon Release 4 Message Queue and optionally dependent on Java ES Web Server or third-party web containers, as described in Application Server Dependencies. However, these are soft upgrade dependencies; upgrade of these components is optional with respect to upgrade of Application Server to Release 4.

Release 4 Application Server is also optionally dependent upon on High Availability Session Store. If being used by Application Server, High Availability Session Store should be upgraded to Release 4. Note that upgrade of High Availability Session Store automatically upgrades the J2SE shared component to Release 4.

Backward Compatibility. Release 4 Application 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 Application 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 Application Server Upgrade

This section describes how to perform an upgrade of Application 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

Before you upgrade Application Server you should perform the tasks described below.

Verify Current Version Information

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

AppServer8-base/bin/asadmin version --verbose

Table 9-3 Application Server Version Verification Outputs
Java ES Release	Application Server Version Number
Release 2	Sun ONE Application Server 7.0.0_03c
Release 3	Sun Java Enterprise System Application Server Enterprise Edition 8.0.0_01
Release 4	Sun Java Enterprise System Application Server Enterprise Edition

Upgrade Application 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, because the upgrade of Application Server to Release 4 does not require upgrading other Release 3 components, this task is optional. If you choose to upgrade components upon which Application Server depends, those components would generally be upgraded in the following order:

Shared Components. Instructions for upgrading Java ES shared components to Release 4 are provided in Upgrading Java ES Shared Components.

Message Queue. Instructions for upgrading Message Queue to Release 4 are provided in Chapter 7, "Message Queue".

Web Container Software (optional). Instructions for upgrading Web Server or Application Server are provided in Chapter 6, "Web Server" and Chapter 9, "Application Server", respectively.

High Availability Session Store (optional). Instructions for upgrading High Availability Session Store are provided in Chapter 8, "High Availability Session Store".

Back Up Application Server Data

The Application 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

You should know the Application Server administrator user ID and password for your currently installed version.

Upgrading Release 3 Application Server (Solaris)

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

Upgrade Considerations (Solaris)

The upgrade of Application Server software to Java ES Release 4 takes into account the following considerations:

Any J2EE components running in an Application Server instance should be shut down before you upgrade that instance. However, if load balancing provides for high availability or scalability, this requirement can be relaxed.

All instances of Application Server running on a single computer (all corresponding to the same installed Application Server image) must be shut down while the patch is being applied to the installed image.

In multiple node deployments, perform the upgrade procedure on each node or computer that hosts Application Server instances.

The Release 4 Application Server upgrade patch for Solaris OS is shown in the following table:

Table 9-4 Patches1 to Upgrade Application Server on Solaris
Description	SPARC Solaris 8, 9, & 10	X86 Solaris 9 & 10
Application Server	119166-10	119167-10
Application Server localization	119024-10	119025-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 Application Server instances residing locally on the computer where the upgrade is taking place.

Obtain the required patches, based on Table 9-4.

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

Shut down all J2EE components running in the Application Server instances that are to be upgraded.

Shut down all Application Server instances on the computer that is to be upgraded.

AppServer8-base/bin/asadmin stop-domain domainName

Apply the appropriate Application Server patch in Table 9-4.

patchadd patch_ID

Modify the asant script.

Rename the existing asant script as asant.bak.

The script is at the following location:

AppServer8-base/bin/asant

Copy the asant.template file from

AppServer8-base/lib/install/templates/ee

AppServer8-base/bin/asant

Edit the script.

Replace the %CONFIG_HOME% token with AppServer8-base/config.

If any manual changes had been made in the original script file (asant.bak), merge them into the new asant script.

Confirm that the patch upgrade was successful:

showrev -p | grep patch_ID

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

Restart the Application Server instances.

AppServer8-base/bin/asadmin start-domain domainName

Upgrading Release 3 Application Server (Linux)

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

Upgrade Considerations (Linux)

The upgrade of Application 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 Application Server upgrade patch for Linux OS is shown in the following table:

Table 9-5 Patches1 to Upgrade Application Server on Linux
Description	Patch ID and RPM names
Application Server	119168-10 sun-asac-8.1.2-10.i386.rpm, sun-asacee-8.1.2-10.i386.rpm sun-ascml-8.1.2-10.i386.rpm, sun-ascmn-8.1.2-10.i386.rpm sun-ascmnse-8.1.2-10.i386.rpm, sun-asdb-8.1.2-10.i386.rpm sun-asdem-8.1.2-10.i386.rpm, sun-asdemdb-8.1.2-10.i386.rpm sun-ashdm-8.1.2-10.i386.rpm sun-asJdbcDrivers-8.1.2-10.i386.rpm sun-asjdoc-8.1.2-10.i386.rpm, sun-aslb-8.1.2-10.i386.rpm sun-asman-8.1.2-10.i386.rpm, sun-asmanee-8.1.2-10.i386.rpm sun-asu-8.1.2-10.i386.rpm, sun-asuee-8.1.2-10.i386.rpm sun-asut-8.1.2-10.i386.rpm, sun-aswbcr-8.1.2-10.i386.rpm
Application Server localization	119026-10 sun-asacee-Locale-8.1.1-51.i386.rpm sun-ascmnse-Locale-8.1.1-51.i386.rpm sun-asu-Locale-8.1.1-51.i386.rpm sun-asuee-Locale-8.1.1-51.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 Application Server instances residing locally 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 9-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

Shut down all J2EE components running in the Application Server instances that are to be upgraded.

Shut down all Application Server instances on the computer that is to be upgraded.

AppServer8-base/bin/asadmin stop-domain domainName

Back up the following files:

all files under AppServer8-base/pointbase/tools/serveroption

AppServer8-base/samples/common.properties

Apply the RPMs for Application Server in Table 9-5.

rpm -Fvh sun-asmodule-8.1.2-10.i386.rpm
rpm -Fvh sun-asmodule-Locale-8.1.1-51.i386.rpm

Restore the files backed up in Step 4 to their original locations:

all files under AppServer8-base/pointbase/tools/serveroption

AppServer8-base/samples/common.properties

Modify the asant script.

Rename the existing asant script as asant.bak.

The script is at the following location:

AppServer8-base/bin/asant

Copy the asant.template file from

AppServer8-base/lib/install/templates/ee

AppServer8-base/bin/asant

Edit the script.

Replace the %CONFIG_HOME% token with AppServer8-base/config.

If any manual changes had been made in the original script file (asant.bak), merge them into the new asant script.

Confirm that the patch upgrade was successful:

rpm -qa | grep sun-as

The new version numbers of the RPMs should be returned.

Restart the Application Server instances.

AppServer8-base/bin/asadmin start-domain domainName

Verifying the Upgrade

You can verify that the patch has been properly applied using the following command:

Post-Upgrade Tasks

Rolling Back the Upgrade (Solaris)

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

Rollback Considerations (Solaris)

The procedure for rolling back the upgrade to Release 4 of Application Server is pretty much the reverse of the procedure for upgrading to Release 4. The patches are removed.

Rollback Procedure (Solaris)

Upgrading Application Server from Java ES Release 2

This section includes information about upgrading Application Server from Java ES Release 2 to Java ES 2005Q4 (Release 4). The section covers the following topics:

Introduction

When upgrading Java ES Release 2 Application Server to Release 4, consider the following aspects of the upgrade process:

General Upgrade Approach. The upgrade is performed by installing Release 4 Application Server using the Java ES installer and choosing the configure later option. Re-configuration is subsequently achieved using the asupgrade utility. Following the Application Server upgrade you have to migrate Release 2 J2EE components and applications to Release 4.

Upgrade Dependencies. Upgrade of any Java ES component on a computer from Release 2 requires the upgrade of all other Java ES components hosted by the computer; selective upgrade of Java ES components from Release 2 to Release 4 is not supported. In particular, all Java ES shared components used by Application Server need to be upgraded. Message Queue must also be upgraded, if residing on the same computer, and if Web Server is being used for load balancing, it also must be upgraded.

Backward Compatibility. Release 4 Application Server is not backwardly compatible with the Release 2 version. J2EE components and applications need to be migrated run in a Release 4 Application Server environment.

Upgrade Rollback. Rollback of the Release 4 upgrade to Release 2 is achieved by simply reverting back to the Release 2 installation (Release 2 configuration data is not removed by the upgrade process).

Platform Issues. The general approach for upgrading Application Server is the same on both Solaris and Linux operating systems.

Release 2 Application Server Upgrade

Pre-Upgrade Tasks

Before you upgrade Application Server you should perform the tasks described below.

Verify Current Version Information

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

Upgrade Application Server Dependencies

The upgrade of Application Server dependencies should include the upgrading to Release 4 of all locally-resident product components upon which Application Server depends. Shared components are upgraded automatically by the Java ES Installer as part of the upgrade procedure (see Step 3).

When upgrading Application Server dependencies, they should be upgraded in the following order, all before you upgrade Application Server. You can skip any that might already have been upgraded.

Back Up Application Server Data

The Application Server upgrade from Release 2 to Release 4 does not overwrite Release 2 configuration data. However, for safe measure, the configuration directory of all Application Server instances should be backed up before performing the upgrade to Release 4.

Obtain Required Configuration Information and Passwords

You should know the following information about your currently installed version:

Upgrading Release 2 Application Server

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

Upgrade Considerations

The upgrade of Application Server software to Java ES Release 4 takes into account the following considerations:

Upgrade Procedure

The procedure documented below applies to all Application Server instances residing locally on the computer where the upgrade is taking place.

su -

Stop all Application Server and related processes.

Install Release 4 Application Server using the Java ES installer, choosing the Configure Later option.

Choose to install at least the first three subcomponents, including the Node Agent component.

Once Application Server software is installed, be sure to perform the post-install procedures provided in Configuring Application Server After a Configure Later Installation.

Identify both target and source installation directories, for example:

Default Release 2 source on Solaris: /opt/SUNWappserver7

Default Release 4 target on Solaris: /opt/SUNWappserver/appserver

Run the asupgrade utility.

The asupgrade utility creates a Release 4 node agent under which it migrates Release 2 Application Server instances.

The utility is located under the Application Server directory, for example:

Upgrade wizard mode: AppServer8-base/bin/asupgrade

Upgrade console mode: AppServer8-base/bin/asupgrade -c

The upgrade wizard or upgrade console will guide you through the upgrade steps.

For more information about the Application Server asupgrade utility, refer to Chapter 3 of the Application Server Enterprise Edition 8.1 Upgrade and Migration Guide 2005Q1 (http://docs.sun.com/doc/819-0222).

Start the Domain Administration Server (DAS).

AppServer8-base/bin/asadmin start-domain --user admin_ID
--password password domainName

Restart upgraded Application Server instances.

Do this by starting the node agent under which the upgraded Application Server instances have been migrated:

AppServer8-base/bin/asadmin start-node-agent --user admin_ID
--password password nodeagentName

where nodeagentName has the form hostName_domainName.
The default domainName is domain1.

Verifying the Upgrade

Start the Admin Console and verify that these servers are started. If any of the servers are not running, check the following log file for failures that might be caused by port conflicts:

If there failures due to port conflicts, use the Admin Console to modify the port numbers to eliminate the conflicts, then stop and restart the node agent.

You can verify the upgrade of Application Serverto Release 4 by entering the following command:

Post-Upgrade Tasks

There are a number of post-upgrade tasks beyond the steps described in Upgrade Procedure. These involve the migration of Release 2 J2EE components and applications to run in a Release 4 Application Server environment and redeploying them to the appropriate Application Server instances.

For more information about migrating J2EE components and applications, refer to Chapter 4 of the Application Server Enterprise Edition 8.1 Upgrade and Migration Guide 2005Q1 (http://docs.sun.com/doc/819-0222).

Rolling Back the Upgrade

The procedure for rolling back the upgrade to Release 4 of Application Server is simply to revert to the Release 2 version of Application Server, which was not removed by the upgrade to Release 4.

Multiple Instance (Cluster) Upgrades:

The Application Server’s asupgrade utility can be used to upgrade multiple instance clusters. For instructions, see Chapter 3 of the Application Server Enterprise Edition 8.1 2005Q2 Upgrade and Migration Guide (http://docs.sun.com/doc/819-2559).

Configuring Application Server After a Configure Later Installation

After a Configure Later installation, you will need to run a script to set the Application Server environment. Use the following steps.

Locate the accessory distribution for Application Server:

Sun Java Enterprise System 2005Q4 Accessory CD 1,
Application Server Add Ons for Solaris SPARC and x86,
CD Image 1 of 1

Accessory contents can be downloaded from the Sun Download Center at http://www.sun.com/software/javaenterprisesystem/get.xml

Refer to the ReadMe file in the Addon folder in the accessory distribution and perform the procedures specified.

Run the postInstall script.

The main script in the Addon folder, postInstall, should be run from the accessory distribution, otherwise some files will not be found.

The scripts configure and create the AppServer8-base/bin/* shell scripts and an config/asenv file from templates that are installed during installation. (Normally the installer creates the bin/* shell scripts, but if Configure Later is chosen, they have to be created as described.)

Create a new domain.

When using the asadmin create-domain command to create a new domain, you specify values for two parameters: adminPort and instancePort. The adminPort value can be the same as that used by the Release 2 server instance, however the instancePort value should not be the same as that used by any of the Release 2 server instances. By choosing an unused instancePort value, you will avoid conflict between the Release 4 DAS instance and the Release 2 server instances that are migrated to Release 4 (see Step 5).

If necessary, modify the environment settings in the AppServer8-base/config/asenv file.

You have to edit the file manually.



Note	To configure Application Server for load balancing, refer to the “Configuring Web Servers for HTTP Load Balancing” section in the “Application Server High Availability Features” chapter of the Sun Java System Application Server Enterprise Edition High Availability Administration Guide (http://docs.sun.com/doc/819-0216).

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