Skip Navigation Links | |
Exit Print View | |
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide |
1. High Availability in GlassFish Server
2. Setting Up SSH for Centralized Administration
3. Administering GlassFish Server Nodes
4. Administering GlassFish Server Clusters
5. Administering GlassFish Server Instances
6. Administering Named Configurations
7. Configuring Web Servers for HTTP Load Balancing
8. Configuring HTTP Load Balancing
9. Upgrading Applications Without Loss of Availability
To Upgrade an Application in a Single Cluster
Upgrading in Multiple Clusters
To Upgrade a Compatible Application in Two or More Clusters
Upgrading Incompatible Applications
To Upgrade an Incompatible Application by Creating a Second Cluster
10. Configuring High Availability Session Persistence and Failover
11. Configuring Java Message Service High Availability
If the new version of the application is incompatible with the old version, use the following procedure. For information on what makes applications compatible, see Application Compatibility. Also, you must upgrade incompatible application in two or more clusters. If you have only one cluster, create a “shadow cluster” for the upgrade, as described below.
When upgrading an incompatible application:
Give the new version of the application a different version identifier from the old version of the application. The steps below assume that the application has a new version identifier.
If the data schemas are incompatible, use different physical data sources after planning for data migration.
Deploy the new version to a different cluster from the cluster where the old version is deployed.
Set an appropriately long timeout for the cluster running the old application before you take it offline, because the requests for the application won’t fail over to the new cluster. These user sessions will simply fail.
Customize the ports for the new instances on each machine to avoid conflict with existing active ports.
The start causes the cluster to synchronize with the domain and be updated with the new application.
For example, for Sun Java System Web Server, the location is web-server-install-dir/https-host-name/config/loadbalancer.xml.