Administration of the AS Java

Use

With a dual-stack system (ABAP and Java) you can perform administration tasks for AS Java from SAP NetWeaver Application Server for ABAP, that is, you can start and stop the AS Java in different ways. You can find the functions in the ICM monitor (transaction SMICM, or from the SAP menu by choosing Start of the navigation path Administration Next navigation step System Administration Monitor System Monitoring Internet Communication Manager End of the navigation path ).

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 Startup Framework for AS Java is used to start, stop, and control the AS Java components.

Prerequisites

You are using SAP NetWeaver 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, Start of the navigation path Goto Next navigation step HTTP Plug-In Application Server Display Data End of the navigation path .

Under HTTP Application Server Handler you can see the following information:

Property	Possible Values	Meaning
`ABAP server operational`	`TRUE` or `FALSE`	Is the ABAP server running? If you execute transaction SMICM from the SAP GUI, this value must be `TRUE` .
`AS Java server state`	`initial`	AS Java is not started
`started`	The instance controller of the AS Java ( jstart process) is started.
`connected`	The instance controller of AS Java has set up the connection to the ABAP Dispatcher, but is not yet active (ready to run). In dev_disp you can see the status CONNECTED.
`active`	At least one Java server process of the instance has been started, and requests can be processed. In dev_disp you can see the status ACTIVE.
`inactive`	No Java server process of the instance can process requests. Reasons for this could be: All server processes are still in the startup phase. All server processes are in the shutdown phase. All server processes are reserved for debugging, or have been removed from load balancing for some other reason. As soon as a server becomes available, ACTIVE and LB=1 should be set.
`down`	AS Java has been stopped.
`ICM attached to AS Java (SF)`	`TRUE (n active server processes)` or `FALSE`	The instance controller of the Startup Framework ( jstart process) creates a shared memory segment. The cluster reports to the ICM that the segment exists, and the ICM attaches itself to the SHM ( “attach” ). If the AS Java is running, this value must be `TRUE` . The number of running Java server processes must be specified.
`Default root access handler`	`ABAP` or `AS Java`	Value of parameter `is/HTTP/default_root_hdl` (compare Message Server Parameters ). Note The parameter is only evaluated if the AS Java is active. Otherwise, the default root handler is always ABAP.
`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 Goto HTTP Plug-In Application Server Load URL Prefixes . You can view the available URL prefixes in `URL Prefix Table`

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 ( Start of the navigation path AS Java Next navigation step Instance (local) End of the navigation path ) and also for the entire Java cluster ( AS Java 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 a SIGQUIT message to the jstart process. The AS Java is then terminated with a soft shutdown. The (ABAP) dispatcher does not actively close the connection; the AS Java shuts itself down once it has finished processing all running requests.

If the application server is restarted, the AS Java is restarted by the Dispatcher.

Sending a Hard 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 a SIGINT message to the jstart process. The AS Java is then terminated with a hard shutdown. The Java processes get a certain amount of time to close and if this does not suffice, they are closed with a hard shutdown. Unlike with a soft shutdown, with a hard shutdown you can guarantee that the AS Java will be terminated after a few minutes.

If the application server is restarted, the AS Java is restarted by the dispatcher.

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 jstart process. This terminates the jstart 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.

Display Status (local only)

Here you can see the status of the local AS Java. The display contains the following information:

Whether the AS Java is configured, and the status of the AS Java.
Values of the profile parameters that set up AS Java