In
Figure
6-1, Access Gateway 1 and Access Gateway 2 have the same configuration except for the
reverse proxy listening address. They share the other configuration settings because they are
members of an Access Gateway cluster. This section explains how to create a group of Web servers,
how to add multiple proxy services and reverse proxies to an Access Gateway, and how to manage a
cluster of Access Gateways.
Section 6.1, "Setting Up a Group of Web Servers," on page 154
Section 6.2, "Using Multi-Homing to Access Multiple Resources," on page 155
Section 6.3, "Managing Multiple Reverse Proxies," on page 164
Section 6.4, "Managing a Cluster of Access Gateways," on page 166
6.1 Setting Up a Group of Web Servers
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
DNS Name:
www.mytest.com
IP Address:
10.10.195.90:80
For this configuration, you use a single reverse proxy and proxy service. To add multiple Web
servers to a host:
1 In the Administration Console, click Devices > Access Gateways > Edit > [Name of Reverse
Proxy] > [Name of Proxy Service] > Web Servers.
2 In the Web Server List section, click New.
3 Specify the IP address or the fully qualified DNS name of another Web server for the "virtual"
group, then click OK.
4 Repeat Steps 2 and 3 to add additional Web servers to the group.
5 To save your changes to browser cache, click OK.
6 To apply the changes, click the Access Gateways link, then click Update > OK.
The Access Gateway can perform a round robin, or it can be configured to perform a simple failover,
sending 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.7.2, "Configuring TCP Connect Options for Web Servers," on page
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
154 Novell Access Manager 3.1 SP1 Access Gateway Guide
Adding Redundant Web Servers
Firewall
Request
Section 1.7.2, "Configuring TCP Connect Options for Web Servers," on page
Access Gateway
1
2
3
test1.com
test2.com
test3.com
60.
60.
Need help?
Do you have a question about the ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE and is the answer not in the manual?
Questions and answers