Using the SAP J2EE Engine with Standalone Dispatcher
In the previously described scenario, an SAP Web AS must always run together with the SAP J2EE Engine, so that the J2EE Engine can be involved in the load balancing mechanism of the
SAP Web Dispatcher.
If, however, you want to use the J2EE Engine without ABAP and the SAP Web AS’s other functions, you can use the standalone dispatcher (
dpj2ee), which does not require a database, any work processes or a SAP gateway. This dispatcher starts all of the necessary processes (ICM, J2EE Engine), connects to the message server and sends this the logon data for HTTP(S) and J2EE(S). The SAP Web dispatcher can get all of the information it needs for load balancing from this dispatcher.From the point of view of the SAP Web AS, this server is not visible and it is not displayed in the server overview in Transaction SM51. This server can therefore take part in load balancing but naturally only for those requests that should be forwarded to the J2EE Engine.
This server requires the same environment as the usual SAP Web AS, that is, a directory structure, profile files and so on. The trace output is written to file dev_j2ee in the work directory.
You must set profile parameter
icm/dpj2ee to TRUE to be able to operate the standalone dispatcher.