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
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
You can perform a rolling upgrade of an application deployed to a single cluster, providing the cluster’s configuration is not shared with any other cluster.
For example:
asadmin> asadmin deploy --enabled=false --target myCluster myApp:1.1
Follow these steps:
For example, for Sun Java System Web Server, the location is web-server-install-dir/https-host-name/config/loadbalancer.xml.
Monitor the load balancer’s log file.
For example:
asadmin> asadmin enable --target instance01 myApp:1.1
Enabling the upgraded application version automatically disables the previous version.
Follow these steps: