0HWD)UDPH$GPLQLVWUDWRUªV*XLGH
8QGHUVWDQGLQJ0HWD)UDPH/RDG%DODQFLQJ
Load balancing allows an application to be published for execution on any of several Citrix servers in a server farm. When a published application or desktop session configured for multiple servers is launched from a Citrix ICA Client, load balancing selects which server will run the application or desktop session based on server load. You can tune how load balancing calculates server load for each server in a server farm using the Load Balancing Administration utility.
The Citrix ICA Client contacts the master ICA Browser to find the address of a server containing the published application. The master ICA Browser maintains a list of servers configured to run the published application. The master browser selects one of the servers based on load and returns the address of that server to the Citrix ICA Client. Each server calculates a separate load level for each network protocol (IPX, TCP/IP, and NetBIOS).
Load balancing supports mixing WINFRAME 1.7 or later and MetaFrame servers in a single server farm.
Use Published Application Manager to configure published applications. See
Chapter 5, “Publishing Applications,” for more information.
1RWH Load balancing is available only when a copy of Citrix Load Balancing Services has been installed on each server that will participate in load balancing.
5HFRQQHFWLQJWR/RDG%DODQFHG6HVVLRQV
Published applications allow a user to run applications or access a desktop session without knowing the name or address of a particular server. If the published application is located on a single server, the user can disconnect and reconnect to the same session.
If the published application is configured to run on multiple servers in a server farm, the user must be reconnected to the same server in the server farm to reconnect to his or her session. The ICA Browser can reconnect the user to his or her previous session on the same server under certain conditions.
When the user attempts to reconnect to the published application, the ICA Client queries the master ICA Browser for the address of the published application. The master ICA Browser checks the list of disconnected sessions. If it finds a disconnected session from the same ICA Client, it returns the address of the server with the disconnected session.
