Monitoring the State of the ICM (SAP Library - Architecture of the SAP Web Application Server)

Monitoring the State of the ICM

Use

This transaction provides various functions for monitoring the state of the ICM and for detecting any possible errors.

Prerequisites

The ICM is running on the application server.

Functions

You can find the functions described here in the Goto menu.

Trace Files

To display or reset the trace file, choose Go To ® Trace File or Go To ® Trace Level. You can also set the trace level here (values can be between 0 and 3; the default is 1).

Parameters

Choose Goto ® Parameters to display or change the ICM profile parameters. If you want to change them, you can display the Rz11 documentation for every parameter that is executed by placing the cursor on the parameter name and choosing This graphic is explained in the accompanying text Documentation.

The value field is ready for input for those parameters that can be changed dynamically.

Caution

Note that with dynamic changes, these are lost the next time the instance is started.

Statistics

Choose Go to ® Statistics to activate, deactivate, display, and reset the ICM statictics.

Memory Pipes

Choose Go To ® Memory Pipes for information on the memory pipes that are used for data exchange between the ICM and the work process.

Host Name Buffer

The mapping of host names to IP addresses or of service names to port numbers is buffered in the SAP System, once they have been read from the file system. If a host name or a service name that should be accessed is changed, the host name buffer must be reset.

Services

You can use this function to monitor and administer services (ports that are used for the ICM connections). This is described in Displaying and Changing Services.

Release Information

Choose Goto ® Release Info or choose Release Info to display information about the version of the ICM, the release and the patch level of the SAP kernel.

The first line contains general information on the ICM.

You can see the status of the SAP kernel from kernel information. As well as the kernel release and compile information, you can find the following numbers.

update level specifies the kernel status with which the kernel can run in an SAP system. If different application servers should run in a system with different kernel patch statuses, they must all have the same update level.

patch number specifies the last patch level that is relevant for the component ICM.

source id indicates (the numbers after the point) the actual kernel patch level.

Below you can find the patch comments on the kernel patches that affect the ICM component, as well as additional detail information.

HTTP Server Cache

Here you can find functions for Monitoring and Administrating the ICM Server Cache.

HTTP Log

Choose Springen ® HTTP Log you can display the following information on HTTP logging.

Display entries: Display the entries in the logging file
Information: Name of the log file, format of the log file, terms for new log files, maximum log file size, cyclical write (yes/no), current number of characters in the log file and the current number of lines in the file.
Write buffer: The logging file entries are buffered and are regularly written to the hard disk. Since you can only see the entries that are already on the hard disk with Display Entries, you can use this function to force the buffer contents to be written to the hard disk.

You can find additional information about HTTP logging in Logging in the ICM.

HTTP Application Server

By choosing Goto ® HTTP App Server you can display information on the HTTP application server (information about the active ABAP or J2EE server, URL perfix table) as well as load URL prefixes.

If no J2EE server has been configured, (J2EE Server configured = FALSE), then all HTTP requests are passed to the ABAP server (to the ICF, see also . Server Roles). If a J2EE server is connected, the URL prefix table is used to decide whether the request is sent to the ABAP or the J2EE server. All URL prefixes in the table are sent to the ABAP server, all others are sent to the J2EE server. The table is determined from the possible prefixes (HTTP service tree and external aliases) of the Internet Communication Framework.

If no J2EE server has been configured, the table is not loaded. You can however enforce this using Load URL Prefixes.

Server Selection and Load Balancing Using the SAP Web Dispatcher