!--a11y-->
SAP J2EE Engine Administration 
You can manage the SAP J2EE Engine from the SAP Web Application Server, that is, you can start and stop it in different ways. You can find the functions in the ICM monitor (Transaction SMICM or by choosing Administration ® System Management ® Monitor ® System Monitoring ® Internet Communication Manager).
With the integrated SAP Web Application Server you can process both ABAP and J2EE requests. Furthermore, the Java Connector JCo provides a narrow coupling between ABAP and Java (see Connectivity and Interoperability).
You are using the SAP Web Application Server with ABAP and J2EE.

So that the dispatcher can start the SAP J2EE Engine, you must set parameter rdisp/j2ee_start to 1. You can make this setting dynamically in Transaction RZ11.
On the initial screen of the ICM monitor (Transaction SMICM), choose Administration ® J2EE Server.
The following functions are available:
The (ABAP) dispatcher of the SAP Web Application Server sets the restart flag for the SAP J2EE Engine and sends the SOFTSHUTDOWN message to the J2EE server. The dispatcher does not actively close the connection, the SAP J2EE Engine must close itself instead. If the application server is restarted, the SAP J2EE Engine is restarted by the dispatcher.
The SAP Web Application Server’s dispatcher sets the restart flag for the J2EE Engine and sends the SOFTSHUTDOWN message to the SAP J2EE Engine. The dispatcher does not actively close the connection, the SAP J2EE Engine must close itself instead. If the application server is restarted, the SAP J2EE Engine is restarted by the dispatcher.
The SAP Web Application Server’s dispatcher sets the restart flag for the SAP J2EE Engine and sends a signal to the process (shell or Java process). If the application server is restarted, the SAP J2EE Engine is restarted by the dispatcher.
This sets the SAP J2EE Engine’s restart flag.
