Skip to Content

Disclaimer

Material in this blog is provided for information and technical features demonstration purposes only. Described decompilation and debugging techniques, even in case they make perfect sense from technical perspective, shall be a subject for assessment and evaluation from legal perspective to avoid violation of software license agreements.

 

Intro

How often have you come across functionality in a SAP PI/PO system (SAP application server Java or SAP standard PI/PO applications, 3rd party vendor or in-house development) and needed to look into its implementation? There may be variety of reasons for that – root cause analysis of an issue, lack of available technical documentation and necessity to understand details of specific functionality realization are just few of them that come to my mind straightaway and that I personally face quite often.

 

Eng Swee Yeoh wrote an excellent document regarding how to get yourself familiar with source code of PI adapter modules using standard functionality of NetWeaver Administrator and Java decompilerю Actually approach described by him goes beyond analysis of only adapter modules and is applicable to different other applications deployed on SAP application server Java. You can read his article at Get your hands on those (precious) module source code!. Some time ago I shared an approach how to find binary files that contain Java classes which we would like to look into – for example, in sake of further decompilation, by means of one of classloader utilities accessible via SAP AS Java Telnet (see How to Find Java Library Resource File Possessing Information for Class Name). These approaches are powerful and suitable if we would like to perform reverse engineering of a Java application by means of its decompilation and subsequent standalone analysis.

 

What if it is required not only to analyze source code, but also to observe its behaviour at runtime? Normally, the applicable approach is to use debugger and debug a Java application in question at runtime. This is relevant and convenient if it is possible to retrieve source code of a debugged application, import it to IDE of your choice and use remote Java application debugging features of that IDE. As I have written earlier, this is not always realistic and we may find ourselves in a situation where we need to debug a Java application for which we don’t have source code or its acquisition (from original development project or decompiled bytecode) is time consuming / requires meaningful efforts. Let’s have a look how to progress with it and achieve desired goal – namely, how to decompile and debug arbitrary Java application executed on SAP application server Java, on-the-fly.

 

It shall be noted that technique described in this blog, is helpful when analyzing non-obfuscated applications. Generally speaking, obfuscation is a process targeted at concealing original source code and making reverse engineering (e.g. based on decompilation) of an application complicated. In Java world, most commonly obfuscators change variables names, manipulate with class names, suppress end of line symbols, etc. – as a result, decompiled code differs a lot from its original source code version and is hardly readable. This is not a limitation relevant to a particular described technique or toolset – decompilation and analysis of obfuscated code is instrumentation agnostic complicating factor. Good news are, obfuscation is not very common technique for SAP PI/PO applications.

 

Another remark that shall be mentioned upfront, is that even in case of decompiling non-obfuscated application, decompiled version of generated source code may not have 100% match in comparison to original source code of an application and may have deviations. A reason for this is, that none of decompilers can produce identical replica of original source code – they are generating source code that will compile into identical binary / bytecode as original source code did. Various Java decompilers use different decompiling engines and algorithms, so even the same bytecode decompiled using different Java decompilers, may result in slightly different generated source code versions. Normally such discrepancies, in case of any, are not too significant and generated source code is helpful when debugging through it and assessing program flow.

 

Having all this in mind, let’s move on to hands-on examples.

 

 

Preparation

First of all, we will need SAP JVM distribution. It can be downloaded from SAP Service Marketplace or retrieved from installed SAP application server Java based system. In examples below, I will use SAP JVM 6.1 (to be more precise, SAP JVM 6.1.085), but newer versions of SAP JVM (versions 7 and 8) are also shipped with this kind of functionality.

 

SAP JVM distribution already contains Java debugger utilities (which are located in the same directory as other core binaries of SAP JVM – /bin/) – we will use one of them, jvmdebugger (SAP JVM Debugger), for debugging an application deployed on SAP PO system. Please note that in earlier patch levels of SAP JVM, jvmdebugger didn’t exist – firstly, its alpha version was introduced – jvmdebugger-alpha. If you use older patch levels and don’t find jvmdebugger, you may want to use jvmdebugger-alpha instead. In newer patch levels, jvmdebugger-alpha was deprecated and removed, and only jvmdebugger was left in distribution.

 

SAP JVM Debugger is a lightweight GUI application that provides major features relevant for Java debugger:

SAP JVM Debugger.png

 

Before using SAP JVM Debugger, please ensure that debug mode is enabled on corresponding server nodes – this can be done for example using SAP Management Console, NWDS, NetWeaver Administrator or SAP JVM utility jvmmon:

Server node debugging mode enabled.png

SAP JVM supports “on-the-fly” debugging (debugging on-demand) – which means, debug mode can be switched on and off without need of system restart, as well as debugger can be connected and disconnected ad hoc. By default, SAP application server Java uses following formula to determine debug port: 5{instance number}20 + {server node index} * 5 + 1. For example, for server node 0 of instance number 00, default debug port is 50021. This can be changed if necessary. Please take a note of a host name (here, sap-po-poc) and debug port (here, 50021) of a debuggee (server node) – I will use them in later examples.

 

Next, in a clustered environment, it is highly recommended to isolate execution of calls that we want to debug, on specific server nodes. Since each server node of a cluster runs its individual JVM process, it is only possible to establish session between debugger and a specific server node (otherwise, it will be necessary to start several debugger instances and connect them to corresponding server nodes, which is not recommended due to increased load on a debuggee system). For some types of requests, this is possible (for example, HTTP requests can be sent to specific server node of a specific instance – see Addressing HTTP Requests to the Specific Server Node in AS Java 7.1 and Higher), but for some others this is not feasible.

 

Last, but not least, please ensure that there are no network security related issues that can prevent debugger from establishing connection to a debug port of a server node. One of most commonly faced issues is firewall settings that allow connections to only specific ports of SAP application server hosts or from only specific hosts.

Options to get connected to a debuggee

There are several options how SAP JVM Debugger can discover and connect to debuggee:

 

  • Connect manually using direct JDWP connection

The most straightforward and basic option is to connect to a debug port of a server node using direct JDWP connection. JDWP stands for Java Debug Wire Protocol, which is a TCP/IP based protocol used by Java debugger and debuggee to communicate to each other. This is a part of Java Platform Debugger Architecture (JPDA), which describes a standardized way for Java debugger and debuggee interoperability, most (if not all) modern Java IDEs and JVMs are compliant with it.

 

In SAP JVM Debugger, select Connect > Connect manually, and enable option “Direct JDWP Connection”. Specify host name (or IP address) and debug port of debuggee (the debug port which is used by corresponding server node – see section above):

Direct JDWP connection.png

 

  • Connect manually via debugger daemon

This option is based on indirect communication between debugger and debuggee, which is mediated by debugger daemon, debugger daemon acts as a proxy. The option is useful if for some reason (for example, security limitations / firewall rules), it is not possible to establish direct connection from debugger to debuggee. Debugger daemon can be started on any host, to which debugger can connect, and from which debugger daemon can connect to debug port of debuggee – which also means, it is not necessary to start debugger daemon on the same host as SAP application server, but it can be started on another host and proxy actual location of a debuggee.

 

Debugger daemon can be started using utility jvmdebugger-daemon, which is a part of SAP JVM distribution. Mandatory argument is port number, which will be used by debugger daemon to listen for incoming calls from debugger. Optionally, it is also possible to specify debuggee details to which debugger daemon will forward debugger calls: basic option – host name / IP address and port, advanced option – SAP system details: instance number and server node VM identifier (in this case, even if debug mode was not enabled for server node explicitly, debugger daemon will enable it implicitly, but it then has to run on the same host as debuggee). If debuggee details are missing in arguments of debugger daemon, then it will be necessary to specify them in SAP JVM Debugger – that’s why, to achieve complete transparency for SAP JVM Debugger not only from network connectivity perspective, but also from connectivity configuration perspective, it is advisable to maintain debuggee details as arguments when starting debugger daemon. On the other hand, if the same debugger daemon is going to be used to proxy debugger calls to several debuggees (for example, several server nodes or even nodes of several instances / systems), then it makes sense to start debugger daemon without debuggee details, and provide debuggee details when configuring connection in SAP JVM Debugger.

 

Debugging connection configuration screen is accessed in the same way, as in the previous option. Ensure that an option “Direct JDWP Connection” is disabled.

 

In examples below, debugger daemon was started on a host E107184, and a port 12345 was chosen as a listener port for it.

 

If debugger daemon is started with listener port and specific debuggee specification:

jvmdebugger-daemon - specific debuggee.png

Then in SAP JVM Debugger, in debugging configuration, an option “Debuggee details already specified in jvmdebugger-daemon” has to be enabled, and only host name (or IP port) and listener port of debugger daemon are to be specified:

Connection via debugger daemon - debuggee in daemon configuration.png

 

If debugger daemon is started with only listener port specification:

jvmdebugger-daemon - no debuggee.png

Then in SAP JVM Debugger, in debugging configuration, an option “Debuggee details already specified in jvmdebugger-daemon” has to be disabled, and host name (or IP port) and listener port of debugger daemon together with host name (or IP port) and debug port of debuggee are to be specified:

Connection via debugger daemon - debuggee in debugger configuration.png

 

  • Discover available JVMs using JVM Browser and connect via jvmmond

This option allows not only to connect to a specific debuggee, but also perform its discovery at the beginning. The option is based on indirect communication between debugger and debuggee, which is mediated by jvmmond daemon.

 

Daemon can be started using utility jvmmond, which is a part of SAP JVM distribution, it shall be started on the same host as debuggee. There are no mandatory arguments for this utility. It is possible to specify port number, which will be used by daemon to listen for incoming calls from debugger – otherwise, it will used default port 1099.

 

In SAP JVM Debugger, select Connect > Connect using JVM browser, and specify host name (or IP address) of a host where jvmmond daemon is started. If non-default port is used, then host name (or IP address) and listener port shall be specified separated with colon. A a result, jvmmond daemon will show a list of discovered JVMs that are running on that host, and their properties:

jvmmond - JVM browser.png

After debuggee server node is found in a list, it can be selected and debug session can can started.

 

There are several advantages of using jvmmond daemon in comparison to other described options:

  • Debuggee discovery and debuggee details acquisition before establishing debug session – this is especially helpful if there are several server nodes running on the same host;
  • Transparency in accessing debuggee – no direct communication between debugger and debuggee;
  • Absence of necessity of explicit enabling debug mode on server node – even if debug mode is not enabled on an accessed server node, jvmmond implicitly enables it when it receives a call from debugger, and disables it after debugger is disconnected;
  • jvmmond daemon can handle and proxy not only debug calls, but also profiling requests (coming from Java profiler – another very important instrument in toolset of a developer and support team).

 

 

I personally prefer debugging / profiling server nodes via jvmmond whenever possible (due to reasons mentioned above), but if there is no possibility to start additional services (like debugger daemon or jvmmond) and debugger can establish connection to a debug port of debuggee, then direct connection via JDWP is also a valid option.

 

 

Debugging

After SAP JVM Debugger established debug session with debuggee using any of options described above, we will see layout that is very traditional to majority of Java debuggers, I will not go into details here.

 

Let me take execution of scenario with REST receiver communication channel as an example for debugging. From variety of options for setting breakpoints, I will set a breakpoint for method entry with default suspension type. In this example, method executeCall() of a class com.sap.aii.adapter.rest.ejb.receiver.RESTReceiverChannel was chosen, being one of critical classes in REST receiver logic execution.

 

Alternatively, I could have used other types of breakpoints – like breakpoint on method exit, breakpoint on specific code line, exception breakpoint, watchpoint, etc., depending on specific needs. Technically speaking, it could be literally any class and any method that is executed by server node – AS Java Engine functionality, PI Mapping Runtime, mapping programs, Adapter Framework, adapter applications, NWA and PIMON applications, or any other deployed applications.

 

I used thread suspension type (the default one). Another option would be to suspend the whole JVM when breakpoint is reached, which is helpful when dealing with multi-threaded applications to keep debugged runtime consistent. Breakpoint suspension type is configurable in properties of a breakpoint, accessible from context menu for a breakpoint.

 

Here is how the set enabled breakpoint looks:

Breakpoint.png

After the breakpoint is set, I run the scenario so that the REST receiver communication channel is called and the breakpoint is reached – as a result, the thread that is executing the communication channel logic, is suspended, and we can analyze its call stack, explore class and instance variables content, step further in execution, etc. – generally speaking, perform common debugging activities as we would have done when doing Java application debugging:

Debugger window.png

 

 

Decompilation

Up to now, we are able to suspend debugged thread (or a complete JVM of a server node that we debug, if necessary), navigate through its call stack and variables, but we are still missing one important part – navigation through debugged code. This is now good time to decompile executed bytecode – and corresponding toolset was built-in SAP JVM Debugger. This is not a typo when I wrote “was” and not “is” – decompiler was built-in SAP JVM Debugger in earlier releases and patch levels of SAP JVM, but then it was intentionally removed from distribution.

 

In SAP JVM Debugger, while being connected to a debuggee and upon reaching a breakpoint and suspending thread / JVM, we can make an attempt to decompile bytecode of a given class by referencing it by its full quantified package and class name:

Decompilation - enter package and class.png

Following earlier example, I enter com.sap.aii.adapter.rest.ejb.receiver.RESTReceiverChannel here. Please note that decompiler doesn’t automatically decompile class, which method is currently executed by a suspended thread. As a result, we have to manually instruct decompiler which class we want to decompile. This also means we are not limited to decompilation of purely the class that is currently executed by a thread – instead, we can decompile literally any valid class that is available for debuggee.

 

In newer versions of SAP JVM distribution, such decompilation attempt is likely to fail with the following error:

Decompilation not supported.png

In earlier releases (for example, in SAP JVM Debugger alpha release), this functionality was not deprecated and removed, and would have resulted in on-the-fly decompilation of the specified class using built-in decompiler (owners of older SAP JVM releases may try this out). In newer releases, this was changed and the decompiler functionality was removed (causing the error message depicted on a screenshot above). Still there is a workaround that can be used to decompile and run through source code even in SAP JVM Debugger versions that don’t have on-the-fly decompilation functionality. The idea of this workaround is to upload source code of corresponding classes into SAP JVM Debugger – decompilation, in its turn, is performed by external tools, and not those embedded into SAP JVM Debugger. Summary of required steps is as following:

Save sources.png

Save sources - Save as.png

  • Upload generated ZIP file into SAP JVM Debugger:

Import sources.png

If classes that we need to decompile, are located in different binaries, it is also possible to specify a folder where all files with decompiled source code are located, or add several ZIP files:

Edit source lookup.png

Source code lookup.png

  • Click on “Goto Source File” – and uploaded decompiled source code will be displayed. The decompiled code is mapped to executed bytecode – which means, proceeding in the program flow and going to next instructions will also take effect and highlight next executed instruction in a source code viewer:

Goto source file.png

Debugger with source code.png

 

As a result of actions described above, we end up with debug session which is connected to SAP application server Java and linked to decompiled source code, and we can now step further across debugged application at runtime and analyze details of its execution.

 

 

It shall also be mentioned here that SAP JVM Debugger can be used not only to run through decompiled source code, but has embedded disassembler and can be used to run through disassembled code. Good news are: we don’t need to involve any external tools – disassembly of a class can be done using SAP JVM Debugger functionality. Even though majority of debugging cases don’t require disassembly and the developer is focused on analysis of decompiled source code, there are some areas and use cases when decompilation is not relevant, and the way to proceed with analysis of a problem is to disassemble executed bytecode. For example, if subject of analysis is JVM core functionality or some lower level / native functions coming beyond boundaries of the executed application – analysis of class loading, Java locking and analysis of object monitor / lock acquisition / release attempts, calls of native functions (for example, interaction with network library or I/O system of a host) are some examples of that. This is a very powerful technique and tool, but its description deserves a separate discussion, so it is not in scope of this blog.

 

 

That’s it for now. Good luck and happy debugging!

To report this post you need to login first.

13 Comments

You must be Logged on to comment or reply to a post.

  1. Eng Swee Yeoh

    ***jaw dropped***

    Wow! Such an amazing blog, Vadim! Thank you so much for sharing such a powerful technique.

    As a matter a fact, I got stuck recently trying to figure out the behavior of some standard PO functionality by analysing the decompiled source codes. It gets particularly tricky to perform static source code analysis when interfaces or abstract classes are used because it’s not always visible which implementation class is being executed during runtime. This powerful technique will allow for runtime analysis and debugging is to a developer what a pen is to a writer (or at least before the dawn of computers) 🙂

    I will definitely try this out and I’m sure I will have some questions later on. But as a start, I want to check with you on the JVM part.

    I tried checking the /bin folder of my local JVM 6.1 installation. I use it as my NWDS’ JDK and was downloaded from the following NWDS site.

    https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/731/doc/prerequisites.html

    It looks like it is version 6.1.007 but it does not seem to have jvmdebugger (or the alpha version) there.

    /wp-content/uploads/2016/03/jvm_900376.png

    Do you know which version onwards has the utility, and when was alpha deprecated?

    Thanks again so much for this.

    Regards

    Eng Swee

    (0) 
    1. Vadim Klimov Post author

      Hi Eng Swee,

      Thank you so much for your feedback and so positive comments, very much appreciated!

      Unfortunately, I haven’t found any notice of SAP JVM Debugger toolset announcement in neither release notes for SAP JVM, nor other official materials like SAP Help or SAP Notes. So I currently see it as a feature which was introduced silently to SAP JVM distribution and then was evolved. And this was also one of driving factors for me to write this blog and share experience of using the embedded debugger. I personally came across this toolset accidentally after one of SAP JVM patching exercises. That time, I could only find debugger alpha version and didn’t know if it will be released or will remain in its alpha state. But when I saw it was promoted to non-alpha, I thought it would be good time to speak out about it. 🙂

      For SAP JVM 6, the first patch level where I saw SAP JVM Debugger (its alpha version), was SAP JVM 6 PL47 distribution:

      JVM 6.1.047.png

      Now I use SAP JVM 6.1 PL85 – even though there is a non-alpha version of SAP JVM Debugger tools, I can still see alpha version is in there (but I don’t use it any more and switched to non alpha):

      JVM 6.1.085.png

      In both cases, distributions of SAP JVM that I used, were for Windows 64 bit.

      Regarding analysis of runtime… I agree it becomes more complex and uncertain when we deal with abstract classes or interfaces that contain multiple implementations and base analysis on static code. I think debugging may be a bit of overhead and overcomplicated solution, if the aim is to find the actual called implementation at runtime – I personally would run profiling of an application in question. If it is SAP PI/PO with SAP JVM, then I would use SAP JVM Profiler, which is shipped by SAP as a part of SAP JVM Supportability Tools plugin for Eclipse and can perform SAP JVM profiling and telemetry information collection (generally speaking, other profilers like YourKit or JProfiler shall also cope with the profiling task – at least, when I used YourKit some time ago, it worked well for SAP PI). Performance hotspot analysis profiling will collect information about called methods and gross/net time for those calls. Which means, we can then find a thread that executed application we are interested in, and investigate its calls stack (rendered as a hierarchy of calls), checking what actual implementing classes were called. It is not as informative as debugging (doesn’t show debugged source code and variables content), but is helpful to fastly identify calls sequence and called classes.

      Regards,

      Vadim

      (0) 
      1. Eng Swee Yeoh

        Hi Vadim

        I managed to download SAP JVM 6.1.085 from SMP and tried out this technique using direct JDWP connection.

        I noticed some quirky behavior while trying to debug through a standard adapter.

        i) After I completed a debugging session, I accidentally clicked Terminate instead of Disconnect and it terminated the whole server and caused it to restart. Fortunately, this is a non-productive server. Extra care have to be taken in this area – definitely don’t do it when one is sleepy!

        /wp-content/uploads/2016/03/term_903354.png

        ii) I can’t seem to add breakpoints when a debugging session has already started (thread suspended for debugging). If I try to, the session no longer becomes responsive to any further debugging (can’t step through codes). I had to resort to putting all the breakpoints before starting the session.

        iii) Each step through the codes takes a while (longer than I’m used to when debugging locally). The combination of this and the above item meant that I had to quit and restart the debugging many times just to get to the breakpoint I want to 🙁

        iv) After adding decompiled source codes, I noticed that sometimes the debugging point does not match against the displayed source code. I managed to figure out that this was due to the generated zipped source codes by JD-GUI. As shown in screenshot below, line 226 of the “original” code was generated to line 290. I didn’t bother finding out why JD-GUI behaved this way as I managed to fix it by editing the generated code so that the line no matches.

        /wp-content/uploads/2016/03/code_903378.png

        Overall, I’m not complaining and happy to have this tool available for troubleshooting (or experimenting 🙂 ).

        Thanks also for the extra info about JVM profiling, will try to read more on that as well.

        Regards

        Eng Swee

        (0) 
        1. Vadim Klimov Post author

          Hi Eng Swee,

          These are all very valid points that you mentioned, thank you a lot for pointing them out!

          I could also observe latency when stepping through executed instructions in debugger session. It was sometimes faster when debugger was started locally on the same host as debuggee (running server node), so it could have been network latency for me in those cases, but still I didn’t get immediate response from debugger.

          Regarding terminate vs. disconnect – yes, that should be taken with caution. “Terminate” in SAP JVM Debugger stands for termination of debuggee (which means, termination of debugged JVM that causes termination of corresponding server node), and not termination of debugger. So it is safer to use disconnect option (even though sometimes it is really required to restart debugged JVM and its termination may be necessary).

          I would also suggest being careful when setting suspension type of a breakpoint – I slightly mentioned in a blog that there are a couple of options how we can suspend debuggee: either suspend only thread that came across a breakpoint, or suspend the whole debuggee (which is, all threads of corresponding JVM). The latter option is helpful when we deal with multi-threaded application and cross-thread dependencies, but in a loaded system that concurrently executes many other threads, suspension of the whole JVM is quite an aggressive debugging approach.

          Regards,

          Vadim

          (0) 
  2. Jelena Perfiljeva

    It’s not my area of expertise (at least not yet 🙂 ), but have to say – really nice blog! Great job on the story, highlighting other SCN content, technical details and writing overall.

    Well done and thanks for sharing!

    (1) 
  3. Markus Tolksdorf

    Hi Vadim,

    actually, decompilation is not allowed for SAP products – just let’s have a look into the appropriate END USER LICENSE AGREEMENT (EULA). For example this part:

    6.2 Protection of Rights. Licensee is not entitled to copy, translate, disassemble, decompile nor reverse engineer the Software or other SAP Materials. Licensee must not create or attempt to create the source code from the object code of the Software or other SAP Materials. Licensee is permitted to back up data in accordance with good information technology practice and for this purpose to create the necessary backup copies of the Software. Backup copies on transportable discs or other data media must be marked as backup copies and bear the same copyright and authorship notice as the original discs or other data media, unless technically infeasible. Licensee must not change or remove SAP’s copyright and authorship notices.

    Best regards,
    Markus

    (0) 
    1. Vadim Klimov Post author

      Hello Markus,

      Thank you for bringing this point to attention, this definitely makes perfect sense from legal perspective. In the blog, I was focused on technical aspects and didn’t mention any legal notices – following your comment, I have updated it and put a disclaimer note. Moreover, this can become relevant not only for SAP standard functionality, but also for deployed 3rd party applications that are protected by similar license agreement.

      Nevertheless, I would not like to encourage or discourage anybody from debugging – it is, as for any other instrument, the right tool for the job, and it remains one of major instruments in the developer’s toolbox. Requirement of reverse engineering and decompilation of SAP standard, or 3rd party, or in-house developed functionality shall not commonly arise if employed functionality is complemented with detailed technical documentation. But let’s face reality: due to variety of reasons, this is not always the case and sometimes is not even realistically feasible (even very detailed and up to date documentation cannot cover literally all possible behaviours of the functionality and contain answers for absolutely all technical questions about it). Ideally, such cases shall be addressed to and resolved by vendor support, but commonly, given sufficient level of skills and knowledge, and very limited timelines for issue resolution, when dealing with small bits and pieces, it may be faster to look into specific code blocks right in the system “on the fly” and progress with issue root cause analysis / development task without putting (or by reducing) risk of project schedule being impacted and delayed, rather then following the formal way of issue escalation to vendor support teams. Or by doing these two in parallel and contacting vendor support together with looking into internals of the functionality of concern.

      Regards,
      Vadim

      (0) 
  4. Erkan Isik

    Hi Vadim,

     

    thanks for your great blog. I have one questions:

     

    I  wanted to debug my Adapter Module, and I want to ask how I have to setup the SAP JVM, because my debug port on PO is active, and I also set a break point on th NWDS Java Code. Or should I add the source code on the SAP JVM?

     

    Thanks in advance,

    Erkan

     

    (0) 
    1. Vadim Klimov Post author

      Hi Erkan,

      If you need to debug the adapter module or another Java EE application for which you already have project in NWDS, then you can use the debugger embedded in NWDS/Eclipse and will not need SAP JVM debugger described in this blog. Debugging on-the-fly makes sense when you don’t have original source code of the project – opposite to this, when project is available in your workspace, it is more convenient to debug from NWDS. For debugging from NWDS, please check SAP Note 952795 and links provided in it – they cover aspects of enabling debugging on the server, as well as preparing debug configuration in NWDS and running it.

      Regards,

      Vadim

      (0) 

Leave a Reply