test

Oracle GlassFish Server 3.0.1 Upgrade Guide

Upgrade Overview

The subsections that follow provide information that you will need when you perform an upgrade.

Supported Releases For Upgrade to GlassFish Server 3.0.1

Upgrade to GlassFish Server 3.0.1 from the following earlier releases of the software is supported:

Note –

GlassFish Server 3.0.1 does not support clustering. Therefore, upgrading from the Enterprise Profile is not supported.

Because the differences between GlassFish Server 3.0.1 and Sun GlassFish Enterprise Server v3 do not affect applications and data, upgrade from Sun GlassFish Enterprise Server v3 is not required.

Upgrade Tool Interfaces

You can use the tool through the command-line interface (CLI) or the GUI.

Upgrade Terminology

The following are important terms related to the upgrade process.

Source Domain Directory

The directory of the server domain from which you are upgrading to the new version (for example, c:\glassfish\domains\domain1).

Target Domains Root Directory

The directory where domains are created on the server to which you are upgrading (for example, c:\glassfishv3\glassfish\domains).

Master Password

The SSL certificate database password used in operations such as GlassFish Server startup. This term refers to the master password of the installation from which you want to upgrade. You need to specify this password if you have changed it from the default value of changeit.

Upgrade Tool Functionality

The Upgrade Tool migrates the configuration and deployed applications from an earlier version of Sun Java System Application Server or Sun GlassFishEnterprise Server to the current version. The Upgrade Tool does not upgrade the binaries of the server. The installer is responsible for upgrading the binaries. Database migrations or conversions are also beyond the scope of this upgrade process.

Note –

Before starting the upgrade process, make sure that you stop all domains in the source server (the server from which you are upgrading) and the target server (the server to which you are upgrading).

Migration of Deployed Applications

Application archives (EAR files) and component archives (JAR, WAR, and RAR files) that are deployed in the source server do not require any modification to run on Oracle GlassFish Server 3.0.1. Components that may have incompatibilities are deployed on GlassFish Server 3.0.1 with the compatibility property set to v2 and will run without change on GlassFish Server 3.0.1. You may, however, want to consider modifying the applications to conform to Java EE 6 requirements.

The Java EE 6 platform specification imposes stricter requirements than Java EE 5 did on which JAR files can be visible to various modules within an EAR file. In particular, application clients must not have access to EJB JAR files or other JAR files in the EAR file unless they use a Class-Path header in the manifest file, or unless references use the standard Java SE mechanisms (extensions, for example), or use the Java EE library-directory mechanism. Setting this property to v2 removes these Java EE 6 restrictions.

Applications and components that are deployed in the source server are deployed on the target server during the upgrade. Applications that do not deploy successfully on the target server must be deployed manually on the target server by the user.

If a domain contains information about a deployed application and the installed application components do not agree with the configuration information, the configuration is migrated as is without any attempt to reconfigure the incorrect configurations.

Upgrade Verification

An upgrade log records the upgrade activity. The upgrade log file is named upgrade.log and is created in the working directory from which the Upgrade Tool is run. Additional information is recorded in the server log of the upgraded domain.