Area Menu

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

This submenu contains the following areas:

Area	Function
Monitor	Overview of existing worker threads More information: Architecture of the Internet Communication Manager (ICM)
Core Thread Status	Overview of the central threads (in contrast to worker threads that process connections).
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.
Trace	Displays, resets, downloads trace file. Sets trace level
Parameters	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
Statistics	Displays statistics
MPI Status	Displays status of MPI communication buffer.
ICM Security Log	Settings for security log, display of log file More information: 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

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)

HTTP Handler Menu

Area	Function
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

ICM

The Web admin interface of ICM contains other areas with ICM-specific functions on the left-hand side.

ICM Menu

Area	Function
Application Server	Returns the following information on the HTTP application server: Configured System Type (system/type): specifies the installation type of the instance. Possible values are ABAP (AS ABAP only), J2EE (AS Java only), 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 then all HTTP requests are forwarded to the relevant server. If AS Java and AS ABAP are active (`system/type = DS`), the ICM decides, using the URL prefix table, whether the request is sent 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 which server the requests without URL prefix are to be sent.
Proxy Connections	Returns the following information: Active JCo Proxy Connections: (Only relevant if AS Java is active) Here you see connections that the Java Connector has opened to other instances or systems. More information: SAP Java Connector Active Proxy Connections: (Only relevant if AS ABAP is active) Here you see connections that were opened by the ABAP work process and which expose ICM to the outside.

Area

Function

Application Server

Returns the following information on the HTTP application server:

Configured System Type (system/type): specifies the installation type of the instance. Possible values are ABAP (AS ABAP only), J2EE (AS Java only), 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 then all HTTP requests are forwarded to the relevant server. If AS Java and AS ABAP are active (system/type = DS), the ICM decides, using the URL prefix table, whether the request is sent 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 which server the requests without URL prefix are to be sent.

Proxy Connections

Returns the following information:

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

Active Proxy Connections: (Only relevant if AS ABAP is active) Here you see connections that were opened by the ABAP work process and which expose ICM to the outside.