Integrating the SAP J2EE Engine (SAP Library - Integrating the SAP J2EE Engine)

Component documentation Integrating the SAP J2EE Engine

Uses

With the SAP Web Application Server 6.20, you can integrate the SAP J2EE Engine in your system.

The architecture of this type of system looks as follows:

This graphic is explained in the accompanying text

You can configure the SAP Web AS so that it:

can only process ABAP requests (such as HTTP(S) requests that should be processed by the ICF) (such as SAP Web AS 6.10)

can process both ABAP and J2EE requests (that is, HTTP(S) requests that should be processed by the SAP J2EE AS) (as displayed in the graphic)

can only process J2EE requests (see also Using the SAP J2EE Engine with the Standalone Dispatcher).

The following graphic displays an SAP system that contains all three types of server.

This graphic is explained in the accompanying text

Integration

To operate the SAP J2EE Engine, the following services must be active in the HTTP service tree (Transaction SICF):

/sap/public/icman The ICM uses this service to forward requests to the J2EE server

/sap/public/icf_info provides the SAP Web Dispatcher with information about the logon groups, server load and so on. These services must be activated so that server selection and load balancing using the SAP Web dispatcher can be carried out.

Internet Communication Framework

Functions

Distributing HTTP Requests Using the SAP Web Dispatcher

The SAP Web Dispatcher must now decide which SAP Web AS will receive the request. Is it a request for the WAS server (ABAP stack) or for the J2EE server (Java stack)? The procedure for this is described in section Server Selection and Load Balancing Using the SAP Web Dispatcher.

Processing HTTP Requests Using the ICM

In the case where the SAP Web AS can process both ABAP and Java requests, (as displayed in the graphic at the beginning of the section), the ICM must decide for each incoming HTTP request whether it should pass the request to the ABAP (the Internet Communication Framework) or to the SAP J2EE Engine for processing.

This is particularly unclear if no SAP Web dispatcher is available to the system. The ICM uses the URL prefix to decide whether this request should be passed to the ICF (ABAP) or to the SAP J2EE Engine. To do this it uses the same process as the SAP Web dispatcher.

Caching in the ICM

You can also use the Internet Server Cache with the J2EE server, in order to store HTTP responses (such as HTML pages or images). The next time, the request can be retrieved directly from the cache.

SAP J2EE Engine Administration

Profile Parameters for the SAP J2EE Engine