You can configure a proxy service to service a “virtual” group of Web servers, which adds load balancing and redundancy. Each Web server in the group must contain the same material. When you create the proxy service, you set up the first server by specifying the URLs you want users to access and the rights the users need for each URL. When you add additional Web servers to the proxy service, these servers automatically inherit everything you have configured for the first Web server.
Figure 6-2 Adding Redundant Web Servers
For this configuration, you use a single reverse proxy and proxy service. To add multiple Web servers to a host:
In the Administration Console, click
> > > > > .In the
section, click .Specify the IP address or the fully qualified DNS name of another Web server for the “virtual” group, then click
.Repeat Step 2 and Step 3 to add additional Web servers to the group.
To save your changes to browser cache, click
.To apply the changes, click the
link, then click > .The Access Gateway Service uses a round robin algorithm to select which Web server to send incoming requests to.
The Access Gateway Appliance can be configured to use round robin, or it can be configured to perform a simple failover. Simple failover sends all the traffic to the first Web server as long as it is available. Traffic is sent to another Web server in the list only when the first Web server is no longer available. To configure this option, see Section 1.6.2, Configuring TCP Connect Options for Web Servers.
Connection persistence is enabled by default. This allows the Access Gateway to send multiple HTTP requests to the Web server to be serviced before the connection is closed. To configure this option, see Section 1.6.2, Configuring TCP Connect Options for Web Servers.
Session persistence is enabled whenever a second Web server is added to the list. This allows a browser to persistently use the same Web server after an initial connection has been established. This type of persistence is not configurable. For more information on persistent connections, see Section 1.6.3, Configuring Connection and Session Persistence.