
The ICM monitor (transaction SMICM) provides various functions for monitoring the status and configuration of the ICM and for detecting any possible errors.
You can find the functions described here in the Goto menu.
Trace Files
Using or , you can display the trace file dev_icm , reset it, or set the trace level (values between 0 and 3 are possible, default is 1). You can also display just the start or the end of the file (the first or last 1000 lines). This is a very useful function for large files. Choose .
You can download the trace file on to your local computer, which is very useful for large files or if you want to store a file or reuse it later. To do this choose .
Security Log
To view the security log , choose . You can also download the security log and display general information about it.
dev_icmbnd
If you want to view the trace file of the external binding program icmbnd, choose
Parameters
Choose
to display or change the ICM profile parameters. If you choose
Change , you can display the RZ11 documentation for every parameter that is executed by placing the cursor on the parameter name and choosing
.
The value field is ready for input for those parameters that can be changed dynamically.
Note that with dynamic changes, these are lost the next time the instance is started.
Statistics
Choose to activate, deactivate, display, and reset the ICM statistics.
Memory Pipes
Choose 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. You can display the buffer contents and reset the buffer. Then the ICM reads the updated data from the file system.
To do this choose or Reset .
Services
Choose to monitor and administer the services (ports that are used for the ICM connections). This is described in Displaying and Changing Services .
Connections
All the connections that the ICM has open at the moment are listed here.
shows the TCP/IP connections that the ICM has open for a client (browser, P4, IIOP, Telnet, SMTP client). Either the ICM accepted the connection or opened it itself I(as HTTP client).
shows virtual network connections. These are only significant when the Virtual Machine Container (VMC) is used: The VM in the work process must be able to roll and therefore the VM is not allowed to open any connections; this task is delegated to the ICM which takes on the role of a proxy.
Proxy connections can also be accepted or opened actively.
For more information, see: SAP Virtual Machine Container
Release Information
Choose 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.
kernel information tells you the release of the SAP kernel. Besides kernel release and compile information, this screen provides the following information:
update level specifies with which kernel releases 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 (the numbers after the point) indicates 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.
You need this information mainly for notifying SAP of any problems that may occur.
HTTP Plug-In
combines all the functions that are connected with the HTTP communication of the ICM.
|
Function |
Menu path |
Description |
|---|---|---|
|
Monitor and administer HTTP server |
|
Provides information about the HTTP application server (current AS ABAP or AS Java, URL prefix table). If AS Java is not configured ( J2EE Server configured = FALSE ), all HTTP requests are passed on to AS ABAP. If AS Java is active, 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 table is determined from the possible prefixes (HTTP service tree and external aliases) of the Internet Communication Framework . If no AS Java has been configured, the table is not loaded. You can however enforce this using Load URL Prefixes . For more information, see: Processing HTTP Requests |
|
Monitor and administer HTTP server cache |
|
Here you can find functions for Monitoring and Administrating the ICM Server Cache . |
|
Create and display server logs |
|
You can display the following information about logging HTTP requests (server).
|
|
Create and display client logs |
|
Functions for client logging of HTTP requests (see functions for server logs). For more information, see icm/HTTP/logging_Client_<xx> |
|
Information about the authentication handler |
|
You can display the following information about the authentication handler.
|
|
Information about the modification handler |
|
You can display the following information about the modification handler.
|