!--a11y-->
Administration of the J2EE Engine 
You can manage the J2EE Engine from the SAP Web AS ABAP, 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 Java requests. Furthermore, the Java
Connector JCo provides a narrow coupling between ABAP and Java (see
Connectivity and
Interoperability).
The Java Startup and Control Framework is used to start, stop, and control the Web AS Java components.
You are using the SAP Web Application Server with ABAP and Java.

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 J2EE Engine and sends the SOFTSHUTDOWN message to the J2EE Engine. The dispatcher does not actively close the connection, the J2EE Engine must close itself instead. If the application server is restarted, the J2EE Engine is restarted by the dispatcher.
The (ABAP) dispatcher of the SAP Web Application Server sets the restart flag for the J2EE Engine and sends the HARDTSHUTDOWN message to the J2EE Engine. The dispatcher does not actively close the connection, the J2EE Engine must close itself instead. If the application server is restarted, the J2EE Engine is restarted by the (ABAP) dispatcher.
The SAP Web Application Server’s dispatcher sets the restart flag for the J2EE Engine and sends a signal to the process (shell or Java process). If the application server is restarted, the J2EE Engine is restarted by the dispatcher.
This sets the J2EE Engine’s restart flag.
