The ICM monitor provides various functions for monitoring the status of the ICM and for detecting any possible errors.
You can find the functions described here in the Goto menu.
To display or reset the trace file dev_icm, 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). 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 Goto ® Trace File ® Display Start or Display End.
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 send it on later. To do this choose Goto ® Trace File ® Save File Locally.
If you want to view the trace file of the external binding program icmbnd, choose Goto ® Trace File ® Display Dev_icmbnd.
Choose Goto ® Parameters 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 Documentation.
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.
Choose Go to ® Statistics to activate, deactivate, display, and reset the ICM statistics.
Choose Go To ® Memory Pipes for information on the memory pipes that are used for data exchange between the ICM and the work process.
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 Goto ® Host Name Buffer ® Display or Reset.
Choose Goto ® Services to monitor and administer the services (ports that are used for the ICM connections). This is described in Displaying and Changing Services.
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.
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 numberspecifies 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.
Here you can find functions for Monitoring and Administrating the ICM Server Cache.
Choose Goto ® HTTP Log you can display the following information about logging HTTP requests. The functions are available for HTTP logging for servers as well as for clients.
· Display Entries: Display the entries in the logging file
· Details: 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 to 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.
By choosing Goto ® HTTP Server you can display information on the HTTP application server (information about the active ABAP or J2EE server, URL prefix table) as well as load URL prefixes.
If no J2EE Engine has been configured, (J2EE Server configured = FALSE), then all HTTP requests are passed to the ABAP Engine (to the ICF, see also . Server Roles). If a J2EE Engine is connected, the ICM uses the URL prefix table to decide whether the request is to go to an ABAP or to a J2EE Engine: All URL prefixes that are in the table go to the ABAP Engine; all others to the J2EE Engine. The table is determined from the possible prefixes (HTTP service tree and external aliases) of the Internet Communication Framework.
If no J2EE Engine has been configured, the table is not loaded. You can however enforce this using Load URL Prefixes.