Administration of the AS Java (J2EE Engine) 
You can manage the AS Java from SAP NetWeaver 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 
).
Integration
Of course, you can also use other administration tools to start, stop, and monitor the AS Java engine (SAP Management Console, and so on.) You can find more information in the Administration Manual for the AS Java.
The Java Startup and Control Framework is used to start, stop, and control the AS Java components.
Prerequisites
You are using the SAP Web Application Server with ABAP and Java.
Note
So that the dispatcher can start the AS Java, you must set parameter rdisp/j2ee_start to 1. You can make this setting dynamically in transaction RZ11.
You can check if the AS Java is actually configured and running by choosing, on the initial screen of the ICM monitor, Goto HTTP Server Display Data .
Under HTTP Application Server Handler you can see the following information.
HTTP Server Details
Property |
Possible Values |
Meaning |
|---|---|---|
ABAP server operational |
TRUE or FALSE |
Is the ABAP server running? If you execute the SMICM from the SAP GUI, this value must be TRUE. |
J2EE server configured |
TRUE or FALSE |
TRUE, if the parameter icm/HTTP/j2ee_0 has a correct value. |
J2EE HTTP port |
Port Number |
Port, on which the J2EE engine receives HTTP and HTTPS requests. The J2EE Engine sends the communication port numbers to the ABAP dispatcher, which then forwards the information to the ICM. |
J2EE HTTPS port |
||
J2EE Server operational |
TRUE or FALSE |
TRUE, if the J2EE Engine has sent the ACTIVE event to the ABAP dispatcher (compare dev_disp) and the icm/HTTP/j2ee_<xx> parameter has a correct value. |
Default root access handler |
ABAP or J2EE |
Value of parameter is/HTTP/default_root_hdl (compare Message Server Parameters). The parameter is only evaluated if the J2EE Engine is configured (J2EE Server configured) and operational (J2EE Server operational). Otherwise, the default root handler is always ABAP (ICF). |
URL Prefix Table loaded |
TRUE or FALSE |
Specifies whether the ICM has loaded the prefix table. You can trigger the loading in the ICM monitor by choosing |
Features
The ICM monitor provides various functions for starting and stopping the AS Java. These can be performed both for the local AS Java on this instance ( Administration J2EE instance (local) ) and also for the entire J2EE cluster ( Administration J2EE cluster (global) .
If the AS Java is not running, these menu options are grayed out.
The most important functions are described below.
Sending a Soft Shutdown (With or Without a Restart)
The (ABAP) dispatcher of the SAP NetWeaver Application Server sets the restart flag for the AS Java and sends the SIGINT signal to the jcontrol process. The AS Java is then terminated with a soft shutdown. The (ABAP) dispatcher therefore does not actively close the connection, the AS Java must close itself instead. If the application server is restarted, the AS Java is restarted by the dispatcher.
Sending a Hard Shutdown (With or Without a Restart)
In this release the hard shutdown behaves the same as the soft shutddown.
Ending the Process (With or Without a Restart)
The (ABAP) dispatcher of the SAP NetWeaver Application Server sets the restart flag for the AS Java and sends the SIGKILL signal to the jcontrol process. This terminates the jcontrol and the AS Java with a hard shutdown. If the application server is restarted, the AS Java is restarted by the dispatcher.
Note
When processes are shut down in this way, the system is no longer able to reach a stable state. Only use this option in an emergency.
Restart Yes/No
This sets the restart flag for the AS Java.
Note
If you set new start to Yes, you can also restart a non-running AS Java. When the (ABAP) dispatcher makes the next periodic check it starts the AS Java.