Administration of AS ABAP

Dynamic Work Processes

New

Dynamic work processes enable the work process configuration of the SAP NetWeaver Application Server (AS ABAP) to be modified in accordance with the current specifications while the system is running. This includes restarting new work processes and closing work processes no longer needed.

Dynamic work processes enable a kind of adaptive computing on the one hand, and on the other hand, enable the system to free itself from deadlocks. They can be seen as a supplement to CCMS operation mode switching (changing the work process type).

The system is configured using profile parameters.

The following are new parameters:

• rdisp/dynamic_wp_check

• rdisp/wp_no_restricted

• rdisp/wp_max_no

• rdisp/configurable_wp_no

• rdisp/max_dynamic_wp_alive_time

You can find documentation about the parameters in transaction RZ11.

The standard system setting specifies that ten dynamic work processes can be started in addition to the configured work processes of various types.

More information: Dynamic Work Processes

Soft Shutdown in SAP Application Server

New

To ensure that no requests or data are lost when ending an SAP instance, use the “soft shutdown” function, also known as “graceful shutdown” . A soft shutdown waits for transactions to be completed in a specific order.

Unlike with a hard shutdown, with a soft shutdown all outstanding requests and transactions are processed before the instance closes. This may take some time with long-running transactions (batch jobs).

Soft shutdown can be triggered in transaction SM51, or from the Management Console (SAP MMC or SAP MC).

More information:

Soft Shutdown in SAP Application Server

Soft Shutdown: Configure Timeouts

Transaction STADWD for Displaying Individual ABAP Statistics Records

New

Use ABAP statistics records to find out which activities are running in your system. This is a log of system activities that is implemented in the ABAP kernel. Every dialog step is logged and recorded with technical information, such as response time, transaction code, or CPU time. These individual statistics records are written in the file system of the relevant instance, and are regularly overwritten (by default, every 48 hours).

ABAP statistics records are therefore well suited to investigating the performance of a system or of an instance in more detail, or, if performance problems occur, to identifying the area causing the problems.

If you want to display ABAP statistics records for performance analysis, you can use transaction STADWD for this purpose as of SAP NetWeaver 7.0 EhP 2.

More information:

Analyzing Individual ABAP Statistics Records

Monitoring with SAP Solution Manager

New

SAP Solution Manager is the new central tool with which you can monitor mixed system landscapes that contain both ABAP and Java components.

All functions for administering the software life cycle are available to you in the form of Work Centers. The Work Centers in the SAP Solution Manager provide you with a precise overview of the IT landscape and allow direct access to all important administration tasks.

The following Work Centers are available to you for monitoring your systems and business processes:

• You can use the System Monitoring Work Center to centrally monitor the SAP system landscape.

• You can use the System Administration Work Center to centrally handle all administrative tasks.

The Computing Center Management System (CCMS) can be used as an alternative to the SAP Solution Manager to monitor a system landscape. For more information, see Monitoring (Overview) .