set/Delete External Debugger:
You can use debugging in order to carry out detailed troubleshooting. With the debugger, you check a given section of code in the Request Handler or an ABAP function module for errors.
Basically, there are two different types of debugging:
· With conventional debugging, you can analyze programs that you call up within your own user session on the server, with breakpoints being set at corresponding points in the coding.
· With external debugging, you can analyze programs that are called up by an external user with HTTP. For the purpose of external debugging, special breakpoints (external breakpoints) are set on the target server.
Two variants are available for conventional debugging: the classical variant and the new (2-processor) variant, which creates a separate session for the debugger. At present, external debugging can only be performed with the classical variant.
This section deals especially with external debugging, as it is generally makes sense to call up an external user completely (with all sent parameters) in one step when investigating ICF processes.
Set/Delete Session Break Points;
If you set a breakpoint in the ABAP Editor, for example, this breakpoint is a session breakpoint. Session breakpoints remain active independently of the existence of a Debugger and are valid for all external sessions of a logon. Within the Debugger, you can convert a debugger breakpoint into a session breakpoint and vice versa.
If the setting Session Breakpoints Active Immediately is checked (via Utilities ® Settings ® ABAP Editor ® Debugging in the ABAP Editor or Object Navigator), you can set a session breakpoint in an external session of a logon to force a running program into the Debugger that runs in the same logon (for example, in an external session) and will process the point at which the session breakpoint was set.
Regards,
Muneesh G.
Bluesky
