SRM Debugging Via WEBGUI

[Former Member]

Hi,

I am trying to debug SRM applications like (BBP_POC and BBPAT05) using ITS. External Debugging is not working in QA Environment. Same works fine in Development systems. Any thoughts on what is causing the problem.

Since it is working in Development box, you ll know that I have followed all the procedure for debugging.Interestingly it doesnt work in QA environment. For testing purpose, I tried to debug a report which is not a service( No SICF config) via webgui. It doesnt stop at the breakpoints either. Not sure what I am missing. Could it be a Basis or Security Issue?

Thanks,

[Former Member]

Hi Sujatha,

Please look at this notes:

Note 451292 - How to use ITS debugger

Note 97301 - ITS Debugger and HTTP Proxies

Regards,

Marcin Gajewski

[Former Member]

When I use Debug Points in Central Instance , it works but not in app servers. As i was using SAP GUI to login using loadbalacing, It was taking me to app servers which was not letting me debug.

[mani_sreedharala]

hello sujatha,

Try to put the breakpoints in all the app servers. you can find the list of appservers in SM51 tcode and also make sure that the external breakpoint is activated for the user and also make sure the ITS parameter Generate ~generateDynpro is set to 1 for the service whcih you want to debug.

Regards,

Mani

[Former Member]

Hi,

How to activate ITS debugging. This may be something that's only available with the Integrated ITS with the 6.40 WAS. To activate debugging for a particular service, do the following:

• Find the name of the ITS service. This will usually be shown in the error message that's thrown (part of the displayed URL), and for EBP, the service names all start with "bbp".

• Login to the ABAP system and execute transaction SICF.

• Navigate to the service. For EBP, all the ITS services are under the following path: default_host -> sap -> bc -> gui -> sap -> its.

• Double-click on the service and click on the pencil to change from display -> change mode.

• Click on "Settings".

• Add parameter ~GENERATEDYNPRO and set the value to 1. You can add this same parameter to older versions of the ITS by editing the properties file (or whatever it's called).

That should activate debugging for that specific service. It may change the way certain things are displayed when you are executing the service in the portal. I've already done this for service bbpsc02 which is the shopping cart service.

Now you have to activate external debugging in the ABAP system by doing the following:

• Execute transaction SE38.

• Choose Utilities -> Settings

• Click on the "Debugging" tab.

• Check the checkbox "Actv." to activate external debugging for your userid (or whatever userid you're using with SRM). You can also choose the Classic Debugger or New Debugger -- I've only used it with the Classic Debugger.

• Now you can go into an ABAP program and set an external breakpoint. It appears that if you just click on the "Stop" icon in the toolbar to set a breakpoint, it does NOT set an external breakpoint. Use the menu Utilities -> Breakpoint -> Set/Delete and it should prompt you if you want an external breakpoint (choose HTTP). Verify that the message in the status bar says that an EXTERNAL breakpoint was set.

I also had to select "classic" debugger.

Hope this helps

Naing Zaw-Tun

[Former Member]

Mani and Naing: Thanks for all your messages. But remember if i am able to do the debugging , i would have followed all the steps you have mentioned. But I need to know why it was doing only when I login to Central instance directly without using Load balancing. I tried putting debug points in all servers in SM51. it didnt help either. The first debug point should always be on the central instance. Weird. but atleast I have a workaround.