The Web Dispatcher and the SAP J2EE Engine SAP BASIS

You can utilize features of J2EE in your application if you integrate the SAP J2EE Engine into your system. The integration is a fairly straightforward process. You'll need to configure the Web AS so that it can process both ABAP and J2EE requests or so that it can process only J2EE requests. Your choice depends on whether you have a dedicated system for J2EE. In order to used the J2EE Engine, you'll need to activate /sap/public/icman and /sap/public/icf_info. Icman is the service ICM uses to forward requests to the J2EE server. Icf_info supplies the web dispatcher with various information needed to carry out load balancing.

When a request is received, the web dispatcher decides if it should be sent to the web application server or the J2EE server. The web application server can process both the ABAP request and a Java request. If the web application server receives a Java request from the web dispatcher, the web application server forwards that request to the SAP J2EE engine. The J2EE Engine and the SAP Web AS must run together in order for the J2EE Engine to leverage the load balancing mechanism. In the event you want to use the J2EE Engine without ABAP and other SAP Web AS functions, an alternative is to run the stand-alone dispatcher dpj2ee. The stand-alone dispatcher doesn't require a database, work process, or a SAP gateway.

It starts the ICM and the J2EE Engine itself and connects to the message server. You'll need to set the profile parameter icm/dpj2ee to TRUE in order to run the stand-alone dispatcher.Before starting the SAP J2EE engine, you'll need to set the rdisp/j2ee_start parameter to 1. This can be done dynamically in the Transaction RZ11. Next, start the ICM monitor (Transaction SMICM). From the opening screen, select Administration J2EE Server to see a list of options for the J2EE Server.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

SAP BASIS Topics