1. GlassFish Server Upgrade Compatibility Issues
2. Upgrading an Installation of Application Server or GlassFish Server
Summary of Upgrade Tools and Procedures
Summary of Tools for Performing an Upgrade
Update Tool and the pkg Utility
Summary of Procedure for Upgrading With Upgrade Tool
Summary of Procedure for Upgrading With Update Tool
Summary of Procedure for Upgrading With the Software Update Notifier
Summary of Procedure for Upgrading With the pkg Utility
Supported Releases for Upgrade to GlassFish Server 3.1
Upgrading From Version 8.x or Older Product Releases
Upgrading GlassFish Server Inside a Closed Network
Performing a Side-By-Side Upgrade With Upgrade Tool
Migration of Deployed Applications
To Upgrade From the Command Line Using Upgrade Tool
To Upgrade Using the Upgrade Tool Wizard
Performing an In-Place Upgrade With the Update Center Tools
To Upgrade Using the Update Tool GUI
Upgrading Installations That Use NSS Cryptographic Tokens
To Perform Post-Upgrade Configuration
To Upgrade PKCS#11 Hardware Tokens
Upgrading Clusters and Node Agent Configurations
Overview of Cluster and Node Agent Upgrade Procedures
To Correct the Configuration of a Node After an Upgrade
Correcting Potential Upgrade Problems
Cluster Profile Security Setting
Cluster Profile Upgrade on Windows
This section explains how to use the three Update Center tools to perform an in-place upgrade to GlassFish Server 3.1 from GlassFish Server 3.0.1 or Enterprise Server v3. Specifically, the three tools explained in this section are:
Update Tool
Software Update Notifier
The pkg command-line utility
Note - GlassFish Server 3.0.1 and Enterprise Server v3 are the only product releases that can be upgraded to the 3.1 release with the Update Center tools. If you are upgrading from any other product release, you must use Upgrade Tool, as described in Performing a Side-By-Side Upgrade With Upgrade Tool.
The following topics are addressed here:
Unlike when using Upgrade Tool, when you use the Update Tool, the Software Update Notifier, or the pkg utility to perform a GlassFish Server 3.1 upgrade, the older source server directories are overwritten with the new target server directories, and the existing configuration and deployed applications are reused in the updated installation.
To perform the upgrade, the user who runs the upgrade needs to have read and writer permissions for the server installation directories.
You can perform an upgrade using the Update Center tools in the following ways:
This procedure explains how to use the graphical Update Tool to perform an in-place upgrade to GlassFish Server 3.1 from GlassFish Server 3.0.1 or Enterprise Server v3. Note that it is not possible to use this procedure with any other product releases.
The Update Tool main window is displayed.
When the upgrade is complete, exit Update Tool.
as-install-parent/glassfish/bin/asadmin start-domain --upgrade domain-name
This upgrades the domain and then shuts down the DAS.
as-install-parent/glassfish/bin/asadmin start-domain domain-name
Next Steps
If your older installation was configured with the Load Balancer Plug-in, you will need to download the latest version of the Plug-in Installer and configure it for use with GlassFish Server 3.1. For more information, see Chapter 7, Configuring Web Servers for HTTP Load Balancing, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide.
Browse to the URL http://localhost:8080 to view the domain-dir/docroot/index.html file. This file is brought over during the upgrade. You may want to copy the default GlassFish Server 3.1 file from the domain1.original/docroot directory and customize it for your GlassFish Server 3.1 installation.
To register your installation of GlassFish Server from the Administration Console, select the Registration item from the Common Tasks page. For step-by-step instructions on the registration process, click the Help button on the Administration Console.
This procedure explains how to use the Software Update Notifier to perform an in-place upgrade to GlassFish Server 3.1 from GlassFish Server 3.0.1 or Enterprise Server v3. Note that it is not possible to use this procedure with any other product releases.
Before You Begin
The Software Update Notifier must be installed and enabled on the GlassFish Server or Enterprise Server release from which you are upgrading. Software Update Notifier installation is typically performed during the initial GlassFish Server or Enterprise Server installation. The Software Update Notifier can also be installed later using Update Tool. For more information about the Update Notifier, refer to the Update Tool online help.
Ensure that GlassFish Server 3.1 is one of the items you select for upgrade. This upgrades the server and selected components to the latest available versions.
as-install-parent/glassfish/bin/asadmin start-domain --upgrade domain-name
This upgrades the domain and then shuts down the DAS.
as-install-parent/glassfish/bin/asadmin start-domain domain-name
Next Steps
If your older installation was configured with the Load Balancer Plug-in, you will need to download the latest version of the Plug-in Installer and configure it for use with GlassFish Server 3.1. For more information, see Chapter 7, Configuring Web Servers for HTTP Load Balancing, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide.
Browse to the URL http://localhost:8080 to view the domain-dir/docroot/index.html file. This file is brought over during the upgrade. You may want to copy the default GlassFish Server 3.1 file from the domain1.original/docroot directory and customize it for your GlassFish Server 3.1 installation.
To register your installation of GlassFish Server from the Administration Console, select the Registration item from the Common Tasks page. For step-by-step instructions on the registration process, click the Help button on the Administration Console.
This procedure explains how to use the pkg utility to perform an in-place upgrade to GlassFish Server 3.1 from GlassFish Server 3.0.1 or Enterprise Server v3. Note that it is not possible to use this procedure with any other product releases.
./pkg image-update
This upgrades the server components to the latest available versions.
as-install-parent/glassfish/bin/asadmin start-domain --upgrade domain-name
This upgrades the domain and then shuts down the DAS.
as-install-parent/glassfish/bin/asadmin start-domain domain-name
Next Steps
If your older installation was configured with the Load Balancer Plug-in, you will need to download the latest version of the Plug-in Installer and configure it for use with GlassFish Server 3.1. For more information, see Chapter 7, Configuring Web Servers for HTTP Load Balancing, in Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide.
Browse to the URL http://localhost:8080 to view the domain-dir/docroot/index.html file. This file is brought over during the upgrade. You may want to copy the default GlassFish Server 3.1 file from the domain1.original/docroot directory and customize it for your GlassFish Server 3.1 installation.
To register your installation of GlassFish Server from the Administration Console, select the Registration item from the Common Tasks page. For step-by-step instructions on the registration process, click the Help button on the Administration Console.