Cleaning up – Sun Microsystems 2005Q2 User Manual
Page 33
/var/opt/sun/appserver/nodeagents/
nodeagent_name/i2/logs/
access/server_access_log
■
Windows Java Enterprise System installation:
install-dir\nodeagents\nodeagent_name\i1\logs\access\server_access_log
install-dir\nodeagents\nodeagent_name\i2\logs\access\
server_access_log
■
Standalone Application Server installations:
install-dir/nodeagents/nodeagent_name/i1/logs/access/server_access_log
install-dir/nodeagents/nodeagent_name/i2/logs/access/
server_access_log
4. Stop the Application Server instance that is serving the page.
a. In the Admin Console, in the left pane, expand Clusters.
b. Click FirstCluster.
c. In the right pane, click the Instances tab.
d. Click the checkbox next to the server instance that served the request and
click the Stop button.
5. Reload the clusterjsp sample application page.
The session ID and session attribute data is retained.
6. Check the access log of the other Application Server instance, and notice that it
is now servicing the request.
The state failover features work because the HTTP session is stored persistently in
the HADB. In addition to the HTTP session state, the Application Server also can
store the state of EJB™ enterprise beans in the HADB.
Cleaning Up
To clean up, you can uninstall the Application Server installation by completing the
steps in
“To Uninstall Completely” on page 34
, or you can simply delete the sample
cluster you have just created by completing the steps in
Chapter 2 • Quick Start for Setting Up High Availability Failover
33