VMC Debugger
Use
The VMC Debugger was developed to simplify Java Debugging if support is required. With the VMC Debugger, you can switch directly from the ABAP Debugger to VMC debugging.
The use of the VMC Debugger is optional. You have, of course, the option to continue to perform debugging with a standard development tool, such as Eclipse, in the future.
Integration
The VMC Debugger runs on the same SAP system on which the VM to be debugged is running, and the source files of the VMC applications can be stored in the database of the SAP system.
Prerequisites
Since the VMC Debugger is integrated into the SAP system, you only require a SAP GUI to display it.
Features
The VMC Debugger offers the following advantages:
● In the same way as ABAP debugging, it differentiates between VMC application debugging and VMC system debugging.
Application debugging allows access to application resources, such as Java threads and Java classes. In system debugging mode, you can access all of the resources of a VMC VM.
● The appropriate Java source files are available in the database and do not need to be localized using the file system.
● You can use “conditional” breakpoints.
In the case of a conditional breakpoint, the Debugger only stops if a certain condition is fulfilled, for example, if a variable has a certain value.
● It can process checkpoint lists.
You can upload a text file containing predefined breakpoints, watchpoints, and exceptions from your PC to the server. You can then activate selected checkpoints from the list. You can also download a text file contain the checkpoints that are currently active from the server to your PC.
● You can go directly from the ABAP Debugger to the VMC Debugger display.
Activities
Navigating in the VMC Debugger