Not able to debug a service

[#1]

Hello all -

I have created a simple read service. But for better understanding, I tried to debug my service, for which I have put one external break-point in my data provider class. Then I have tried to run the service, it executed successfully without stopping at break-point. Then I have tried to keep a break-point for the ICF node through SICF transaction, that also didn't work for me.

Need your expert advice on this.

P.S. - Just a thought, can it be a security issue? Though I have checked SU53 (everything was fine there as well).

Thanks -

Kuntal

[ganesh_padala2]

When you create the end-point add user-id/pwd (http basic auth) in transport security, this way to make the service call you will need to pass a user-id and password and then if you have set a external-breakpoint for your user-id then it should stop.

WHat is the tool you are using to make the service call?

[goutham_nagarajnaidu]

Hi Kuntal,

There is no security setting as such on service level to debug,

check in which client you have put the debugger,and for which client your service authenticated when you executed from the browser(client).

Best Regards,

  Goutham

[former_member376453]

Thanks Goutham for your reply. Yes I can understand there is no setting in service level. But the same can be imposed in dialog user authorization level. in the demo box, we have only one client so the both these are targeted to a single system only.

Please let me know, if there is any mandatory setting for the same.

Thanks - Kuntal

[former_member184867]

Hi Kuntal,

One trick can be to execute your URL with parameter sap-ds-debug=true, and to find the stack trace of the call. In this case the URI would look like <Service URI>/<Collection>?sap-ds-debug=true

From the stack trace you can verify once if you are putting your break point at the correct place.

Regards,

Atanu

[bradp]

Hi Kuntal,

I had a similar problem and found that the when the user executing the code was not the user I was logged in with, it was an RFC user account. So maybe check which user the RFC destination is using and make sure the external breakpoint is set for the correct user.

You could always try and put an infinite loop in your code and resume debugging from SM50. This way you can be certain its going to that bit of code and can see which user its executing it with.

Hope that helps.

Cheers,

Brad

[former_member376453]

Thanks Atanu. I have already checked that, everything looks good, but control is not stopping at my code.

Thanks - Kuntal

[former_member376453]

Hi Bradley -

Thanks a lot, that can be a reason. I will check and update the thread accordingly.

Thanks -

Kuntal