Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

- Previous: Upgrading In a Single Cluster
- Next: Upgrading Incompatible Applications

## Upgrading in Multiple Clusters

### To upgrade a compatible application in two or more clusters:

1. Save an old version of the application or back up the domain.

   To back up the domain use the `asadmin backup-domain` command.

2. Turn off dynamic reconfiguration (if enabled) for all clusters.

   To do this with Admin Console:

   1. Expand the Configurations node.

   2. Click the name of one cluster’s configuration.

   3. On the Configuration System Properties page, uncheck the Dynamic Reconfiguration Enabled box.

   4. Click Save

   5. Repeat for the other clusters

   Alternatively, use this command:

   `asadmin set --user` user `--passwordfile` password_file cluster_name`-config.dynamic-reconfiguration-enabled=false`

3. Redeploy the upgraded application to the target `domain`.

   If you redeploy using the Admin Console, the domain is automatically the target. If you use `asadmin`, specify the target `domain`. Because dynamic reconfiguration is disabled, the old application continues to run on the clusters.

4. Enable the redeployed application for the clusters using `asadmin enable-http-lb-application`.

5. Quiesce one cluster from the load balancer

   1. Disable the cluster 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` . Dynamic reconfiguration must be enabled for the load balancer (by setting the `reloadinterval` in the load balancer configuration), so that the new load balancer configuration file is loaded automatically.

   4. Wait until the timeout has expired.

      Monitor the load balancer’s log file to make sure the instance is offline. If users see a retry URL, skip the quiescing period and restart the server immediately.

6. Restart the disabled cluster while the other clusters are still running.

   Restarting causes the cluster to synchronize with the domain and update the application.

7. Test the application on the restarted cluster to make sure it runs correctly.

8. Re-enable the cluster in load balancer:

   1. Enable the cluster 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.

9. Repeat steps 5 through 8 for the other clusters.

10. When all server instances have the new application and are running, you can reenable dynamic reconfiguration for all clusters again.

- Previous: Upgrading In a Single Cluster
- Next: Upgrading Incompatible Applications

- © 2010, Oracle Corporation and/or its affiliates