Show TOC

Configuring AS Java for DebuggingLocate this document in the navigation structure

Context

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 Console perspective in SAP NetWeaver Developer Studio.

Procedure

  1. In the Developer Studio, open the SAP Management Console perspective: choose Start of the navigation path Window Next navigation step Open Perspective Next navigation step Other Next navigation step SAP Management Console End of the navigation path.
  2. In the SAP Management Console perspective, you can browse the registered SAP systems. Browse to Start of the navigation path <your SAP system> Next navigation step <your Java instance> Next navigation step AS Java Next navigation step Process Table End of the navigation path.
  3. In the Process Table , select the server process you want to use, and choose Start Debug Session in its context menu.
  4. 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 the system ones are to 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 is excluded from the load-balancing mechanism in AS Java. This means that application requests which come from nondebugging sessions are not 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) are to be migrated to other server processes.
  5. To confirm the settings, choose Next , then choose Finish .

Results

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.