Managing a web application's state in a clustered environment can be challenging. By default, web application, session, and server variables that are stored in memory or a repository during a user session do not persist during a server redirection. Consequently, the web server cannot maintain the application's state correctly.
To overcome this problem, ClusterCATS provides a session-aware load-balancing feature that lets you maintain application state in a clustered environment.
One way to maintain your web application's state is to create session variables that are stored on the web server. For an e-commerce website that is clustered, it is vital that users do not get redirected to another server in the middle of their session. If they did, their online transactions would be interrupted, making for an unsuccessful and frustrating user experience.
To ensure that users are not redirected from the server on which they start their session, ClusterCATS provides a built-in feature for enabling session-aware load balancing. Sometimes referred to as a "sticky" server, session-aware load balancing guarantees that users will not get bumped from the server on which they start their session until the session is complete, regardless of the load thresholds that have been defined for that server.
Note: Session-aware load balancing may not work if you use absolute hyperlinks in your web pages. Absolute links route the HTTP request back to the cluster entry point and redirect according to the current load threshold without regard to the state of the requesting client. To avoid inadvertent loss of state, use only relative linking in your web pages.
This section describes the following:
The cluster Properties dialog box appears.
The Cluster Member List page appears:
The Cluster Administration page appears: