This transaction provides monitoring, analyzing, and troubleshooting functions.

This means that trace and debugging functions are available when accessing the SAP System via HTTP. Use transaction SICF to access the functions.

The following functions are available.

Use Edit ® Debugging to switch HTTP debugging on and off for a particular user in the current client.

If debugging is active, a new mode is created showing the ABAP debugger when the corresponding URL is entered. The ABAP debugger can then be used to debug the handler.

You have two ways to set HTTP breakpoints, which you can also combine.

• You can specify the virtual host and the path part. If this is contained in the URL, an HTTP breakpoint is set for the service in the first line of the HTTP request handler.
• If you specify a handler class, a n HTTP breakpoint is set in the first line of this class.

In the popup for activating debugging, you can also make the following entries:

• Only calls from SAPGUI-IP. If this option is checked, debugging is only activated if the HTTP client (usually the browser) is running on the same IP address as the SAPGUI of the active system. This prevents many HTTP users from debugging sessions other than their own.
• Validity period: how long debugging should be active under the specified conditions.

There are the following types of breakpoints:

• HTTP Breakpoints: The debugger is called if you have passed the location when processing an HTTP request.
• Session Breakpoints: These are the usual ABAP breakpoints. The debugger is displayed if you pass the location when processing an ABAP program.

There are two ways of setting the HTTP breakpoints. In the ABA peditor, you can activate HTTP debugging. With every breakpoint that you set, the system asks whether it should be an HTTP or a session breakpoint.

The other option is described above.

 Debugger Not Responding

Sometimes the debugger may not open, even though debugging is activated. There are a number of possible causes of this. Try the following:

• If you have selected Only Calls from SAPGUI-IP, deselect it.
• Execute the report RSBREAKPOINTS in se38 and check the breakpoints set for your users.
• Specify the exact URL you want to debug.
• Also check the system debugging. The debugger should now open.

• Protocol: you can use traces both for HTTP and SMTP communication.
• URL path: prefix for the path where the trace should be created.
• Validity duration: length of time the trace should be active for this path (if it is not deactivated by Trace ® Deactivate).
• Only calls from SAPGUI-IP. If this option is checked, debugging is only activtaed if the HTTP client (usually the browser) is running on the same IP address as the SAPGUI of the active system. This prevents many HTTP users from debugging sessions other than their own.
• Trace level: you can set trace level 2 or 3.

You can then deactivate the trace and view it using Edit ® Trace ® Display Trace.

You can use Edit ® Runtime Analysis to activate runtime analysis for the current user. The same popup appears as for the trace (exception: trace level).

If you want to display the runtime analysis, open transaction se30 and choose Other File on the entry screen. Enter SAPSYS as the user. You can then select a request from the list and view the runtime.

Use Edit® Server Monitor to display which of the executed functions are activated, either for the current server or for the entire SAP System.

Since these functions effect performance, it is recommended that you monitor the settings and deactivate settings that are no longer needed.

In this example, the local view has been selected. Trace and runtime analysis are both activated for one user, and debugging is not active.