JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle GlassFish Server 3.1-3.1.1 High Availability Administration Guide
search filter icon
search icon

Document Information

Preface

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

Application Compatibility

Upgrading In a Single Cluster

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

12.  RMI-IIOP Load Balancing and Failover

Index

Upgrading In a Single Cluster

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.

To Upgrade an Application in a Single Cluster

  1. Deploy the upgraded application to the cluster in a disabled state and with a new version identifier.

    For example:

    asadmin> asadmin deploy --enabled=false --target myCluster myApp:1.1
  2. Perform the following steps for each server instance in the cluster.
    1. Quiesce one server instance in the cluster from the load balancer.

      Follow these steps:

      1. Disable the server instance using asadmin disable-http-lb-server.
      2. Export the load balancer configuration file using asadmin export-http-lb-config.
      3. Copy the exported configuration file to the web server instance’s configuration directory.

        For example, for Sun Java System Web Server, the location is web-server-install-dir/https-host-name/config/loadbalancer.xml.

      4. Wait until the timeout has expired.

        Monitor the load balancer’s log file.

    2. Enable the upgraded application version on the quiesced server instance.

      For example:

      asadmin> asadmin enable --target instance01 myApp:1.1

      Enabling the upgraded application version automatically disables the previous version.

    3. Test the upgraded application on the server instance to make sure it runs correctly.
    4. Re-enable the server instance in load balancer.

      Follow these steps:

      1. Enable the server instance using asadmin enable-http-lb-server.
      2. Export the load balancer configuration file using asadmin export-http-lb-config.
      3. Copy the configuration file to the web server’s configuration directory.