Use this procedure to remove only the FirstCluster (the sample highly-available cluster) and the sample application used during this exercise.
Stop the Application Server processes and clean up configuration:
asadmin stop-cluster FirstCluster
asadmin remove-ha-cluster --hosts hadb_hostname,hadb_hostname FirstCluster
Replace the hadb_hostname variable with the host name of the machine where HADB is to run. If you are using just one machine, you must name it twice.
asadmin disable-http-lb-server FirstCluster
asadmin delete-http-lb-ref --config MyLbConfig FirstCluster
asadmin delete-http-lb-config MyLbConfig
asadmin delete-instance i1
asadmin delete-instance i2
asadmin delete-cluster FirstCluster
asadmin undeploy clusterjsp
Stop the web server instance acting as load balancer by running the stop program in:
Rename the loadbalancer.xml file in web_server_install_dir/https-hostname/config to loadbalancer.xml.sav
Stop the HADB Management Agent by one of the following methods:
In a Solaris or Linux Java Enterprise System installation:
In a Windows Java Enterprise System installation:
In a stand-alone Solaris or Linux Application Server installation:
In a stand-alone Windows Application Server Installation:
Congratulations! You have now completed the Quick Start for Application Server.
In this section, you have installed, configured, and started HADB and configured a cluster and an application to use high availability. You have also cleaned up so that your system is ready for other work. See Where to Go Next for additional information on Application Server.