Before starting debugging, you need to make sure that the target server process of AS Java is in debug session. This is done using the SAP Management perspective in SAP NetWeaver Developer Studio.
In SAP NetWeaver Developer Studio, open the SAP Management perspective (
)In the SAP Management perspective, you can browse the registered SAP systems. Browse to
.In the Process Table (right pane) choose the server process you want to use, and in the context menu choose Start Debug Session.
Configure the debugging options listed in the following table and choose Next.
Property |
Description |
---|---|
Suspend |
If selected, all visible threads started by AS Java are suspended when the debugging process starts. If the Code Isolation option is not selected, that is you have not specified particular application threads to be debugged, the server becomes unavailable. |
Code Isolation |
If selected, you start debugging only threads of a particular application. If this option is not selected, all threads, including system threads will be debugged. In this case the whole server process is restarted after the process of debugging has finished. |
Load Isolation |
If selected, the current server process will be excluded from the load-balancing mechanism in AS Java. This means that application requests coming from non-debugging sessions will not be passed to that server process. |
Session Migration |
If selected, all sessions that are not bound to the current server process (for example, if the application does not request programmatically a connection to a particular server host) will be migrated to other server processes. |
To confirm the settings, choose Finish.
When the server enters debug mode, you can see this reflected in the Debug column of the Process Table properties. The value in that column is now:
<username>@<remote host> (<port>)
It shows that the process is now reserved for debugging by that user.