| Configuring the WSM using Device Manager |
|
In an SLB environment, client traffic comes across the Internet to a WSM virtual server IP address. The WSM balances this traffic among the available real servers.
In any authenticated Web-based application, the WSM must provide a persistent connection between a client and the Web server to which it is connected. Because HTTP does not carry state information for these applications, it is important that the browser be mapped to the same real server for each HTTP request until the transaction is complete. This ensures that server load balancing does not send mid-session client traffic to a different real server, forcing the user to restart the entire transaction.
Persistence-based SLB enables you to configure the network to redirect requests from a client to the same real server that initially handled the request. Persistence is an important consideration for administrators of e-commerce Web sites, where a server may have data associated with a specific user that is not dynamically shared with other servers at the site. In the WSM, persistence can be based on source IP address, cookies, and the Secure Sockets Layer (SSL) session ID.
See also:
|
|