Show TOC

Background documentationArea Menu Locate this document in the navigation structure


The area menu is located on the left-hand side of the Web Administration Interface and is divided into subareas. The last menu item is different depending on whether you are operating an ICM or a Web dispatcher.

Core System

The core system contains the runtime environment and infrastructure, and is used by both the Web dispatcher and the Internet Communication Manager (ICM).

Core System Menu (Core System Menu)

This submenu contains the following areas:

Core System (Web Dispatcher and ICM)




Overview of the existing worker threads (see architecture of the ICM)

Core Thread Status

Overview of the central threads (in contrast to worker threads that process connections).

More information about architecture: Internet Communication Manager (ICM)

Active Services

Monitors, starts, and deactivates active services (ports). Changes however are lost when system is restarted. To make permanent changes use profile parameter icm/server_port_<xx>.

Active Connections

Connections currently active.


Displays, resets, downloads trace file. Sets trace level


Displays values of profile parameters in the ICM/Web dispatcher environment.

Host Name Buffer

Displays values of the Host Name Buffer, and resets the buffer.

Release Information

Displays release notes


Displays statistics

MPI Status

Displays status of MPI communication buffer.

ICM Security Log

Security log settings, log file display (see icm/security_log)

HTTP Handler

This area contains the functions of the HTTP handler that is part of both the ICM and Web dispatcher.

Note Note

You can only make changes in this menu if you access the Web admin interface with a user from group admin. You can ascertain whether you have this administration authorization beneath the area menu (Admin rights granted) or in the user overview (admin handler, see below).

More information: Creating Administration Users (use command line)

End of the note.

HTTP Handler Menu (HTTP Handler Menu)

HTTP Module (Web Dispatcher and ICM)



Access Log

Displays parameters and protocol file.

Server Cache

Displays parameterization and cache entries.

Access Handler

Configuration of access restrictions; see icm/HTTP/auth_<xx>.

Admin Handler

Display, create, change, and delete administration and monitoring users for the Web admin interface.

You can see where the file is in which the user data is defined. To create and mange users choose Change Users in the context menu (right mouse button).

Modification Handler

You can see where the rules for modifying HTTP requests are defined. Modifications are used, or instance, to manipulate header fields, filter requests, and rewrite URLS. More information: Modifications of HTTP Requests

Dispatching Module (Web Dispatcher only)

The dispatching module is the part of the SAP Web Dispatcher that selects the application server. The server is selected depending on the protocol, configuration, load balancing procedure, and so on.

The Web admin interface of an SAP Web dispatcher still contains the following areas on the left-hand side:

Dispatching Module Menu (Dispatching Module Menu)

Dispatching Module (Web Dispatcher only)



Monitor Application Servers

Displays current application servers in the system, divided into ABAP and Java (tab pages ABAP and JAVA). Instances that provide both appear in both views.

The following information is displayed for each instance:

  • Name: Name of the instance With the context menu (right mouse button) you can deactivate and reactivate application servers here also. Inactive servers do not get any requests from the Web dispatcher. You can also sent ping requests (HTTP and HTTPS) to each server.

  • Host name: Name of the host on which the instance is running

  • HTTP/HTTPS Connections: HTTP(S) port of the application server, maximum number of HTTP(S) connections that the Web Dispatcher can open to the server, current number of existing connections and maximum number of connections since startup.

  • Requests: Number of requests that the instance has received from the Web Dispatcher. There are the following types of request:

    • Stateful: Stateful requests forwarded to the server that has already processed the request. With stateful requests load distribution only takes place for the first request, and all subsequent requests must be forwarded to the same server.

    • For Group: Requests that are distributed within one logon group.

    • Stateless: Requests that are distributed among all possible instances.

  • Capacity: Capacity of an Application Server. You can overwrite the capacity value by choosing Edit Capacity Values from the context menu. Values that have been overwritten in the context menu are flagged.

    This fixes the values and they can no longer be changed by the system (neither periodically nor in Reload Web Dispatcher configuration).

    You can remove the fixed values by choosing Unlock Capacity Values from the context menu.

  • Load: Load factor, refer to Server Selection and Load Balancing Using the SAP Web Dispatcher

  • Response Times: Response times in microseconds (last average time (calculated from the last 30 requests) and minimum time (since instance was started up))

  • Last Ping Time: Last measured ping time in microseconds

Monitor Server Groups

Displays current server groups for ABAP, J2EE. Displays response times, availability of servers, load factor (see Server Selection and Load Balancing Using SAP Web Dispatcher)

With the context menu (right mouse button) you can deactivate and reactivate application servers here also. Inactive servers do not get any requests from the Web dispatcher.

You can also sent ping requests (HTTP and HTTPS) to each server.

SSL End To End Dispatching

Displays parameters and entries in the client IP table (see End-to-End SSL)

URL Mapping

Displays the URL mapping table (see Architecture and Functions of the SAP Web Dispatcher)

URL Filter

URL filter settings (see SAP Web Dispatcher ass URL Filter)


Displays parameters specific to the Web dispatcher (see Profile Parameters of the SAP Web Dispatcher).

Session Dispatching

Details about session dispatching (default setting is deactivated). For more information see Determining the Server Group.

SAP Web Dispatcher with Multiple Systems

You can also operate the Web Dispatcher with more than one connected system. In this case the menu options Monitor Application Servers, Monitor Server Groups and URL Mapping are displayed for each system separately:

Dispatching Module Menu for Two Systems (Dispatching Module Menu for Two Systems). In this example, the Web Dispatcher is placed before the BCO and D36 systems.

More information: SAP Web Dispatcher for Multiple Systems

ICM (ICM only)

The Web admin interface of an ICM still contains the following areas with ICM-specific functions on the left-hand side:

ICM Menu (ICM Menu)



Application Server

Provides following information about the HTTP application server:

  • Configured System Type (system/type): Specifies the installation type of the instance. Possible vaues are ABAP (only AS ABAP), J2EE(only AS Java) or DS(dual-stack, ABAP+Java)

  • AS ABAP operational: TRUE / FALSE

  • AS Java operational: TRUE / FALSE

  • ICM attached to AS Java (Startup Framework): TRUE / FALSE

  • Number of Active AS Java Server Nodes: <n>

  • AS Java state: <state>

  • Default Root Access Handler: ABAP / J2EE

  • URL Prefix Table Loaded: TRUE / FALSE

If only ABAP or only Java is configured, all HTTP requests are forwarded to the relevant server. If both AS Java and AS ABAP are active (system/type = DS), the ICM uses the URL prefix table to decide whether the request goes to AS ABAP or to AS Java: All URL prefixes in the table are sent to AS ABAP, all others are sent to AS Java.

The Default Root Access Handler (parameter is/HTTP/default_root_hdl) decides to which server requests without a URL prefix go.

Proxy connections

Delivers the following information:

Active JCo Proxy Connections: (Only relevant if AS Java is active). You can see the connections that the Java connector has opened to other instances. More information: SAP Java Connector

Active Proxy Connections: (Only relevant if AS ABAP is active. Here you can see the connections opened by the ABAP work process and sent externally through the ICM.