Sun Microsystems 2005Q2 Verifying Http Session Failover, To Verify Http Session Failover

Page 32

4. Once the instances are stopped, click Start Instances.

Verifying HTTP Session Failover

The steps for testing session data failover are similar for testing load balancing as described in the topic “Verifying Load Balancing” on page 20. This time Session Data is preserved after failure. Failover is transparent to the user because the sample application is configured for automatic retry after failure.

▼To Verify HTTP Session Failover

Steps 1. To display the first page of the clusterjsp application, type this URL in your browser:

http://localhost:web_server_port/clusterjsp

Replace the localhost variable with the name of the system that the Web Server is running on.

Replace the web_server_port variable with the value of the port attribute of the LS element in web_server_install_dir/https-hostname/config/server.xml. For this example, port 38000 is used.

A page similar to what you saw in “To Verify the Application Deployment” on page 16 appears.

2.Examine the Session and Host information displayed. For example:

■Executed From Server: localhost

■Server Port Number: 38000

■Executed Server IP Address: 192.18.145.133

■Session ID: 41880f618e4593e14fb5d0ac434b1

■Session Created: Wed Feb 23 15:23:18 PST 2005

3.View the server access log files to determine which application server instance is serving the application. The log files are located here:

■Solaris Java Enterprise System installation:

/var/opt/SUNWappserver/nodeagents/nodeagent_name/i1/logs/ access/server_access_log

/var/opt/SUNWappserver/nodeagents/nodeagent_name/i2/logs/ access/server_access_log

■Linux Java Enterprise System installation:

/var/opt/sun/appserver/nodeagents/nodeagent_name/i1/logs/ access/server_access_log

32Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Quick Start Guide

Page 31 Page 33
Image 32
Page 31 Page 33
Contents Sun Microsystems, Inc Network Circle Santa Clara, CA 050727@12762 Contents Quick Start for Setting Up High Availability Failover Variable Names and Default Paths Quick StartAbout Application Server Administration To Start the Domain on Solaris and Linux Starting the Domain Administration ServerStarting the Server To Start the Domain on Windows Logging in to the Admin Console To Log In to the Admin ConsolePress a key to close the message window Steps 1. Type this URL in your browserPage To View the Domain Administration Server Log File Examining the Log FileSteps 1. In a terminal window, type this command When you are prompted, provide the master passwordCreating a Cluster To Start the Node AgentYou see a screen like this Click OK. The create process can take a few minutes Deploying an Application To Deploy the Sample ApplicationTo Start the Cluster To Verify the Application DeploymentClick OK Steps 1. Type the following URL in your browserSetting up Load Balancing Installing Web Server Software Creating a Load Balancer Configuration Installing the Load Balancer Plug-inTo Install the Load Balancer Plug-in Starting Load Balancing Verifying Load BalancingTo Create an Http Load Balancer Configuration Export the configuration to a file loadbalancer.xmlTo Verify Load Balancing Http//localhostwebserverport/clusterjspAdd a name and value pair Name=Name Value=Duke for storing Cleaning UpTo Uninstall Completely Uninstall the Application Server To Remove the Sample Cluster OnlyWhere to Go Next Quick Start for Setting Up High Availability Failover Hadb Preinstallation Steps About High Availability ClustersTo Configure Your System for Hadb Starting Hadb Installing HadbTo Install Hadb Run the command to start the agent Steps 1. Change to the /etc/init.d directoryTo Start Hadb in a Stand-Alone Installation on Windows Run the command to start the agent ma -i ma.cfgConfiguring a Cluster and Application for High Availability To Configure a Cluster and Application for High AvailabilityRestarting the Cluster To Restart the ClusterOnce the instances are stopped, click Start Instances Verifying Http Session FailoverTo Verify Http Session Failover Cleaning Up A stand-alone Windows Application Server Installation To Remove the Sample Cluster Run the command to stop the agent ma -r Rename the loadbalancer.xml fileWhere to Go Next

2005Q2 specifications

Sun Microsystems, a company renowned for its innovative technologies and commitment to open standards, reported its second quarter financial results for the fiscal year 2005 (2005Q2) on May 10, 2005. During this quarter, Sun continued to focus on its primary mission of delivering reliable and robust hardware and software solutions, notably in the domain of enterprise computing.

One of the standout features of Sun's offerings during this period was the continued evolution of their UltraSPARC processors. The UltraSPARC IV and IV+ processors represented significant advancements in performance, offering superior computational power and efficiency for enterprise applications. These processors were built on the SPARC architecture, which is known for its scalability and reliability, making them ideal for mission-critical workloads.

In 2005Q2, Sun also emphasized its commitment to the Solaris operating system. Solaris 10 was lauded for its enhanced security features, extended virtualization capabilities, and advanced resource management tools. The introduction of features like DTrace, ZFS, and Time Slider exemplified Sun's dedication to providing customers with enhanced system insight and flexibility. These innovations positioned Solaris as a leading choice for enterprises looking to optimize their IT infrastructure.

Sun's software portfolio saw significant developments, particularly in the realms of Java technology and the Sun Java System. The company continued its advocacy for Java as a universal programming platform, recognizing its pivotal role in the burgeoning field of web services and distributed computing. Sun's development tools and application servers, such as the Sun Java System Application Server, provided developers with robust resources for building and deploying enterprise applications.

Moreover, the company made strides in network performance through its Sun Network.com initiative. This program was aimed at enhancing the deployment of managed services and offered customers solutions designed to improve network efficiency and reliability.

Financially, Sun Microsystems reported revenue growth during this quarter, driven by increased demand for their products and services. The company’s focus on open-source solutions and partnership strategies allowed it to attract new clients and expand its market presence, reinforcing its role as a key player in the technology sector.

In summary, 2005Q2 marked a significant period for Sun Microsystems, characterized by cutting-edge technologies, a strong software ecosystem, and a focus on delivering value to enterprise customers. Through its innovative hardware and commitment to open standards, Sun continued to influence the trajectory of computing in a rapidly changing technological landscape.
Top Page Image Contents