Debugging
Use
Problems that occur when you display or execute BSP applications can be caused by all sorts of different reasons. If a problem occurs, you can debug to find the solution.
A special HTTP debugger is available for the coding in your BSP application. You can use HTTP debugging in exactly the same way as usual debugging.
HTTP debugging is user-specific, that is, breakpoints are set user-specific.
Debugging is not possible for a public or Internet user.
If it is set for the HTTP request, authentication must be carried out.
See also:
You
can find additional information about debugging in the
Debugger
documentation.
You can also set breakpoints for BSP page fragments.
If the debugger does not help you, you can use a trace for your BSP application. To do this, you can either use ICM Tracing or HTTP Browser Tracing.
Prerequisites
Before you debug, ensure that:
·
The
Internet Communication
Manager (ICM) is active.
To do this, go to Transaction
SMICM: The ICM status should be running and you should see a green
stoplight 
.
The ICM is running with the correct parameters (see also
Parameterizing the ICM
and the ICM Server Cache).
· The correct domain or DNS configuration is specified for your BSP application.
See also Note 434918
Activities
You can set or activate HTTP debugging for BSPs in different ways:
·
By setting a
breakpoint 
in your BSP application
· When maintaining the HTTP service tree (Transaction SICF)
Choose Edit → Debugging →Activate Debugging.
You can find additional information in
Monitoring and
Troubleshooting Functions.
· In the development workbench (Transaction SE80).
Choose Utilities → Settings. On the following dialog box for the user-specific settings, on the tab ABAP Editor choose the embedded tabstrip HTTP Debugging and activate HTTP debugging globally for your user.
In the Web Application Builder of the development workbench, you can also activate or deactivate HTTP debugging:
Choose Utilities → Breakpoints →(De)activate for HTTP user.
Ensure that deleting all breakpoints does not automatically deactivate HTTP debugging.