Using an Intermediary Server to Connect to the J2EE Engine

When establishing your cluster network infrastructure, you can establish a demilitarized zone (DMZ) separated by using firewalls to control access to your more critical systems in the backend. Use an intermediary server in the DMZ to perform the necessary routing and load balancing tasks. See the figure below:

Using an Intermediary Server

Supported intermediary servers include:

·        SAP Web Dispatcher

The SAP Web dispatcher is a load-balancing device provided free-of-charge to SAP customers that operates using the SAP application server load-balancing mechanisms. It supports the use of SSL for securing connections and does have URL filtering capabilities. It can be used with both ABAP and J2EE installations.

·        Microsoft Internet Information Server (IIS) with the IIS proxy module

If you are using the Microsoft IIS as the intermediary server, you need to install and configure the IIS proxy module provided by SAP. This proxy module is an ISAPI filter that establishes the connection from the IIS to the J2EE Engine. It also supports the use of SSL for the connection to the J2EE Engine.

·        Other devices (for example, an Apache reverse proxy)

You can also use different devices as the intermediary server, for example, an Apache Web server as a reverse proxy. Such devices often provide additional features such as more refined load-balancing, or request and content filtering. The features provided depend on the product you are using.

See also:

·        SAP Web Dispatcher

·        Configuring the IIS as the Intermediary Server

·        Configuring the Apache Web Server as the Intermediary Server