The web server configuration determines how Access Gateway handles connections and packets between itself and the web servers. For more information about web Server configuration, see Section 2.7.4, Configuring Web Servers of a Proxy Service
On the Home page, click Access Gateways > Edit > [Name of Reverse Proxy] > [Name of Proxy Service] > Web Servers.
The session stickiness provides information about the web server session connection details.
Enable Session Stickiness: By default this option is selected. This option makes the proxy server to use the same web server for all fills during a session.
If your browsers are capable of sending HTTP 1.1 requests, configure the following field to match your web servers:
Enable Force HTTP 1.0 to Origin: Indicates whether HTTP 1.1 requests from browsers are translated to HTTP 1.0 requests before sending them to a web server. If your browsers are sending HTTP 1.1 requests and your web server can only handle HTTP 1.0 requests, you must enable this option.
When enabled, Access Gateway translates an HTTP 1.1 request to an HTTP 1.0 request.
To enable SSL connections between a proxy service and its web servers, select Connect Using SSL. For configuration information for this option, Web Server Trusted Root, and SSL Mutual Certificate, see Configuring SSL between the Proxy Service and the Web Servers.
In Connect Port, specify the port that Access Gateway must use to communicate with the web servers. The following table lists some default port values for common types of web servers.
|
Server Type |
Non-Secure Port |
Secure Port |
|---|---|---|
|
Web server with HTML content |
80 |
443 |
|
WebSphere |
9080 |
9443 |
|
JBoss |
8080 |
8443 |
To control how idle and unresponsive web server connections are handled and to optimize these processes for your network, select TCP Connect Options. For more information, see Configuring TCP Connect Options for Web Servers.
To add a web server, click New in the Web Server List and specify the IP address or the fully qualified DNS name of the web server.
The web servers added to this list must contain identical web content. Configuring your system with multiple servers with the same content adds fault tolerance and increases the speed for processing requests. For more information, see Setting Up a Group of Web Servers.
New: Click to create a new web server. Specify the web Server IP Address or DNS.
After creating the web server in the list, you can configure it as primary server and prioritize the list of web servers based on your requirement.
Delete: Click to delete the selected web server.
If you delete a web server, all web servers which are corresponding to the device in the cluster get deleted.
For Simple failover policy, the web server list is ordered allowing selection of the primary web server.
The common use case is having the same list of web servers and primary designate in all Gateway Appliances in a cluster. However, is some scenarios, you might want Gateway Appliances in a cluster to have different configuration for the above, one of them being locations separated geographically, each hosting Gateway Appliances, as well as some of the web servers. For such cases, select the individual member from Cluster/Cluster Member, and configure the primary and other web servers for each.
NOTE:When an administrator opts for member change, the administrator cannot change the priority of web servers from the cluster. Other operations such as add, delete can be performed.
Primary Web Server: The web server that serves all the requests for this service. Only applicable for simple failover.
Group Web Servers: The web servers that are added at the cluster level will be common and displayed in all cluster member groups. For more information, see Configuring Web Servers at the Cluster Level and Configuring Web Servers at the Member Level.
To save your changes to the browser cache, click OK.
To apply your changes, on the Home page, click the Access Gateways link, and click Update > OK.