on 04-18-2020 1:13 PM
Hi SAP folks,
I've an issue with debugging a WebDynpro application which is being called from the portal , I tried setting various break points like external ,hard coded and user specific but they didn't trigger .
Here is the scenario:
We've a portal application and which is calling a WebDynpro application in the backend SAP system.
Our portal application using the common UID , let's assume: BATCH_USR , which is a common id for the portal users to access this WebDynpro application in the backend SAP system
I'm logging in into SAP system with UID, let's assume : 11****14 and setting breakpoints , I also tried user breakpoint with the batch username BATCH_USR.
I understand that , because my WebDynpro application is being called from the BATCH_USR , the breakpoints I set through the SAP UID are not triggering in the backend SAP system, and I can't trigger debugger for BATCH_USR because it's a 'System' user not a 'Dialouge' type user.
I've verified SICF services , for our WebDynpro component , the log on data is set with the UID: BATCH_USR and procedure filed as: Required with logon data. , Security requirement as: SSL.
Is there any workaround or any way to debug this kind of scenario ?
Hi Vijay
Presuming you have the authorisations, just use transaction SU01 to change user BATCH_USR and change the User Type to Dialog in the Logon Data tab of SU01
Then change it back System again after your debugging is complete.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mark,
Thanks for your reply.
I'm pretty sure that the above mentioned solution can work in DEV/TEST environments with the right authorizations, and it also needed password for BATCH_USR (Depends on the security configurations for the application and the user authentication).
I used a FM to trigger debugging session for the BATCH_USR with my SAP system UID login and able to finish the job.
Thank you so much for your response and help.
Hi Vijay
I assume you're debugging in a non-production environment, so why not try just setting BATCH_USR to a dialogue user just during the debug session.
Hope that helps
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
75 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.