Integrating the SAP J2EE Engine
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:
You can configure the SAP Web AS so that it:
The following graphic displays an SAP system that contains all three types of server.
To operate the SAP J2EE Engine, the following services must be active in the HTTP service tree (Transaction SICF):
See also:Activating and Deactivating an ICF Service Internet Communication Framework
Distributing HTTP Requests Using the SAP Web Dispatcher
TheSAP 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 (theInternet 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 theInternet 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.
See also:Using the SAP J2EE Server with the Standalone Dispatcher SAP J2EE Engine Administration Profile Parameters for the SAP J2EE Engine