In this configuration, the reverse proxy server is deployed in a DMZ between the Web browsers and the application server.

The figure below shows an example configuration that uses a reverse proxy deployed in a DMZ for Web server integration.

Figure 3-4 Example configuration using a reverse proxy deployed in a DMZ for Web server integration

For other examples, see 3.2 System configurations, in the uCosminexus Application Server System Design Guide.

Features

• Only the reverse proxy server accesses the application server, preventing direct access to it from Web browsers.
• Usually, the reverse proxy does not store static content such as HTML.

Flow of requests

Access to the servlet and JSP from the clients goes through one Web server containing the reverse proxy module and another containing a redirector module.

A load balance cluster can be used for load balancing by using a load balancer (layer 5 switch) for the reverse proxy server and the application server.

The following figure shows an example load balance cluster configuration using reverse proxies deployed in a DMZ.

Figure 3-5 Example configuration (load balance cluster) using reverse proxies deployed in a DMZ for Web server integration

For other examples, see 3.2 System configurations, in the uCosminexus Application Server System Design Guide.

Features

• Only the reverse proxy servers access the application servers, preventing direct access to them from Web browsers.
• Usually, the reverse proxies do not store static content such as HTML.
• Scalability and availability can be ensured by distributing loads between the reverse proxy server and the application server.

Flow of requests

Access to servlets and JSPs from the client goes through the first load balancer, the Web servers containing the reverse proxy modules, the second load balancer, and then the Web server containing the redirector module.

For access from Web browsers, the first load balancer distributes the load between the two reverse proxy servers. For access from the reverse proxy servers, the second one distributes the load between the two application servers. The second load balancer also manages HTTP session such as affinity or sticky.

Note that when using HTTPS, you need to install an SSL accelerator in front of the first load balancer.

The following section describes the software and processes required for the machines.

(a) Reverse proxy server machines

Install Cosminexus HTTP Server on the reverse proxy servers. The process shown below should always be activated.

• Web servers

Each Web server should incorporate a reverse proxy module.

(b) Application server machines, management server machine, and client machine

The necessary software and processes to be activated on the application server machines, the management server machine, and the client machine are the same as those for system configurations that use a servlet and JSP as access points. See 3.4.1 System configuration with a servlet and JSP serving as access points (for Web server integration), in the uCosminexus Application Server System Design Guide.