Debugging

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.

For more information, see:

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 tihs you can either use ICM Tracing or HTTP Browser Tracing.

Before you debug, ensure that:

• The Internet Communication Manager (ICM) is active.

  To do this, branch to transaction SMICM: The status of ICM should be running and the green traffic light should be displayed. The ICM is running with the correct parameters (see also Parameterizing the ICM).

• The correct domain or DNS configuration is specified for your BSP application.

  See also SAP Note 434918 .

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 . For further information, refer to Error Handling and Monitoring.

• 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 .

  Caution

  Ensure that deleting all breakpoints does not automatically deactivate HTTP debugging.