Configuring AS Java for Debugging
Use
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.
Procedure
...
1. In SAP NetWeaver Developer Studio, open the SAP Management perspective (Window → Open Perspective → Other → SAP Management).
2. In the SAP Management perspective, you can browse the registered SAP systems. Browse to <your SAP system> → <your Java instance> → AS Java → Process Table.
3. In the Process Table (right pane) choose the server process you want to use, and in the context menu choose Start Debug Session.
4. In the confirmation dialog that appears you have two options:
¡ Choose OK and continue with the pre-selected debugging options. By default, this is the Code Isolation option (refer to the table below).
¡ Choose Expert Mode and configure the debugging options. These are as in the following table:
Debugging Properties
Property |
Description |
Suspend |
If selected, the threads started by AS Java will not be displayed together with application threads during debugging. |
Code Isolation |
If selected, requests for the target application will be sent to the current server process only. |
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. |
Result
When the server enters debug mode, you can see this reflected in the Debugcolumn 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.