A standard error handling mechanism is implemented in the ICM and Web dispatcher. You can however configure both components so that a different error handling mechanism suitable for your application area is used.
Error situations that occur in the back end are not handled by the ICM/Web Dispatcher. If, for instance, an HTTP error 404 (file not found) occurs in the file access handler of the ICM/Web Dispatcher, an error page is returned if one is configured. But if the request goes to the Application Server ABAP (because of the URL) and the requested file is not found in the Internet Communication Framework (ICF), the ICM forwards the error page generated by the ICF to the browser.
If the ICM or Web dispatcher finds an error, in most cases it returns a static text to the browser:
The ICM/Web dispatcher also behaves like this when it is in Maintenance Mode).
If this error page is too detailed for you due to security reasons, you can set profile parameter is/HTTP/show_detailed_errors to FALSE. The details will then be suppressed and the page will look like:
You can also configure the ICM and the SAP Web dispatcher so that they return dynamic error pages.
The following section describes how you do this.
● Under Error Codes you can find the name of the errors that ICM and Web dispatcher know of.
● You can create a default page or a separate page for each error (static or dynamic). More information: Setting Up Error Pages.
An example of a dynamic error page can be found here.
If parameter icm/HTTP/error_templ_path is not set, the ICM static error page is always returned.
If parameter is set, when error <ERRNAME> occurs, the ICM or Web dispatcher first checks whether file ICMERR‑<ERRNAME>.html is located in the directory specified by icm/HTTP/error_templ_path, and sends it to the client. If it cannot find this file, it searches for ICMERR<>.shtml and returns it.
In no specific error page can be found, the ICM returns the default error page ICMERR-EDEFAULT.{html,shtml}(see above). If this file also does not exist, the static page is returned.
For reasons of
performance, the ICM or Web dispatcher checks once the error templates that
are available. This is why you must restart the ICM if you add new templates
(changes to the templates are recognized). You can use the Web Administration
Interface to restart the web dispatcher, or the ICM monitor to restart the
ICM (Transaction SMICM) (see Monitoring the ICM
Using the ICM Monitor).