The following table provides an overview of the various troubleshooting procedures in the ICF environment. By following the links, you can call up detailed descriptions for each tool:
ICF Troubleshooting Tools: Application cases (server)
Problem / Purpose of troubleshooting |
Tool |
Procedure
|
ICF Configuration |
||
ICF service is not running properly (HTTP request handler) |
Activate the debugging function for the required service using transaction SICF.
The path always begins with the first node below the virtual host. |
|
ICF service cannot be executed at all (ICF runtime problems, logon error) |
Activate the trace function for the required service using transaction SICF.
The path always begins with the first node below the virtual host. |
|
The called alias (or the corresponding target service) cannot be executed |
Choose Edit → Parse URL in transaction SICF and enter the desired path name.
The path always begins with the first node below the virtual host. |
|
Incorrect data is received (request) or sent (response) |
Activate the ICF recorder recordings and then carry out the analysis.
The path always begins with the first node below the virtual host. |
|
|
ICF profile Parameter Maintenance (Transaction RZ11) |
Check the relevant profile parameters in transaction RZ11 and make any necessary adjustments. |
Performance / System load |
||
Analysis of work processes, DB calls, memory usage at the transaction level in the active SAP system |
Call transaction STAD and perform the relevant analyses. |
|
General performance problems in the active SAP system, |
Call transaction ST05 and perform the relevant analyses. |
|
Performance analysis at service level |
Activate the runtime analysis with transaction SICF. To evaluate the analysis, choose transaction SE30. |
|
Performance problems over distributed components in a system landscape (analysis required at transaction level) |
Call transaction STATTRACE and perform the relevant analyses.
This transaction uses DSRs and passport technology to collect and display raw data |
|
System overload in the active SAP system |
Call transaction ST03N and perform the relevant analyses. |
|
System overload in a landscape with more than one system (SAP and non-SAP) |
Call transaction ST03G and perform the relevant analyses.
This analysis provides you with aggregated system data |
|
ICF/ICM Communication |
||
Processing of HTTP requests by the internet and the communication manager |
Call transaction SMICM and analyze the relevant trace and log files. |
|
General server problems |
||
HTTP requests cannot be received / processed due to load distribution problems |
Call transaction SMMS and analyze the relevant trace and log files. |
|
Troubleshooting by SAP Support |
||
The service tree for transaction SICF contains a number of test services for troubleshooting by SAP.
These services are only intended for internal SAP troubleshooting purposes and must not be used for any other purposes. |
/default_host/sap/bc/echo
/default_host/sap/bc/error
/default_host/sap/bc/srt/xip/sap |
Provides information about the logon procedure in use, header and form fields, and the SSO cookie generated for the processed request.
Creates various error scenarios in the System.
Used to solve the Web Service error message Could not determine WSDL address (ICF_ERROR), SRT_REG038 in connection with XI services.
These services should only be activated for troubleshooting carried out by SAP Support. |