How to debug portal webdynpro appl

Hi Experts,
We are running some issue in QA box with Portal WebDynpro application using R/3 as back-end and for that we need to debug the application at R/3 side.
In Dev environment we used to put infinite loop in BAPI and debug it via SM50.
Anyone knows the other way to debug since we dont want to make changes in R/3 code?
Any pointers on this will be very helpful.
Regards,
Mehul

Hi Mehul,
In r/3 system go to se37. Open ur function module ->display. put an external breakpoint in the module. Execute ur webdynpro application.U can debug from there.
regards
Sumit

Similar Messages

How to debug Portal application?

Hi,
I am developing a weblogic console extension application with web logic portal framework, I got some error, but no idea how to debug,
I can see some error on buildApplication.jsp file, but can't find __buildapplication.java file which is compiled from buildApplication.jsp,
so I can't know the error is in which line in buildApplication.jsp file. and I dont' even know which tag is tag1 tag2 tag3 in that jsp file.
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag3(__buildapplication.java:292)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag2(__buildapplication.java:260)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag1(__buildapplication.java:211)
at jsp_servlet._ext_jsp.__buildapplication._jspService(__buildapplication.java:138)
Code of buildApplication.jsp:
     <fmt:setBundle basename="detwds" var="current_bundle" scope="page"/>
     <beehive-template:template templatePage="/layouts/configBaseLayoutNoTransact.jsp">
          <beehive-template:section name="configAreaIntroduction">
          <fmt:message key="buildApplication.jsp.page.introduction" bundle="detwds"/>
          </beehive-template:section>
          <beehive-template:section name="form">
          <html:xhtml/>
          <wl-extension:template name="/templates/jmxform.xml">
          <wl-extension:form name="ExtensionForm" type="com.det.consoleext.form.ExtensionForm" action="/BuildApplication" bundle="detwds">
          <wl-extension:select
          property="contents"                                                   labelId="buildApplication.jsp.page.repositoryList.label"                                                   inlineHelpId="buildApplication.jsp.page.repositoryList.inlinehelp"
          singlechange="false">
               <wl-extension:optionsCollection                                                                  property="repositoryName"
                    label="label"
                    value="value"/>
          </wl-extension:select>
          </wl-extension:form>
     </wl-extension:template>
     </beehive-template:section>
     </beehive-template:template>
Error message:
2755> <BEA-423405> <An exception [java.lang.String] was thrown while rendering the content at [ext_jsp/buildApplication.jsp].
java.lang.ClassCastException: java.lang.String
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag3(__buildapplication.java:292)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag2(__buildapplication.java:260)
at jsp_servlet._ext_jsp.__buildapplication._jsp__tag1(__buildapplication.java:211)
at jsp_servlet._ext_jsp.__buildapplication._jspService(__buildapplication.java:138)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at org.apache.beehive.netui.pageflow.scoping.internal.ScopedRequestDispatcher.include(ScopedRequestDispatcher.java:119)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:551)
at com.bea.netuix.servlets.controls.content.NetuiContent.beginRender(NetuiContent.java:363)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:483)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__flowlayout._jspService(__flowlayout.java:281)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:332)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:306)
at com.bea.netuix.nf.UIControl.render(UIControl.java:578)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:482)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:146)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:62)
at jsp_servlet._framework._skeletons._default.__gridlayout._jspService(__gridlayout.java:285)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:528)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:454)
at com.bea.netuix.servlets.controls.application.laf.JspTools.renderJsp(JspTools.java:123)
at com.bea.netuix.servlets.controls.application.laf.JspControlRenderer.beginRender(JspControlRenderer.java:72)
at com.bea.netuix.servlets.controls.application.laf.PresentationControlRenderer.beginRender(PresentationControlRenderer.java:65)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:479)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:518)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:529)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:220)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:375)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:341)
at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:188)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:142)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:377)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:253)
at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:206)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:191)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:124)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

Hello,
Debugging a JSP using a stack trace is made possible by using the keepgenerated element of the jsp-descriptor element in your web app descriptor in WEB-INF/weblogic.xml. The working-dir and verbose elements are also of interest.
You can edit weblogic.xml or you can use the Oracle WebLogic Server console to configure your web app. In the console you would go to "Deployments", find your web app, select the "Configuration" tab, Lock & Edit, and do your thing. The settings you are interested in are "Debug Enabled", "JSP Keep Generated", and "JSP Verbose". I'm not sure which weblogic.xml element the "Debug Enabled" corresponds to, but it might be something like the debug-enabled element of the session-descriptor element.
I can never remember where JSP generated servlet source code files end up if I have not specified a working dir. They end up buried DEEPLY. I just search the file system in my workspace for the generated files. For example, I just found the generated source for my helloOne.jsp in:
C:\bea_wlp102\user_projects\workspaces\frmwrk\.metadata\.plugins\org.eclipse.wst.server.core\tmp0\frmwrk_domain\work\MyWAR\jsp_servlet\_portlets\__helloone.java

How to debug the webdynpro application

Hi ,
i am facing a problem for debugging web dynpro application from offshore (my server is located in onsite) and i connected using VPN and also i changed my SDM Debug Mode to ON and also enable debugging of process also but it is giving error message like this
<b>Failed to Connect to remote VM.Connection Refused</b>

Hi Nageswara
The link provided shows you hoe to debug WebDynpro application.
Its a eLearning course available on sdn, which shows step by step process.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/3178ae74-0701-0010-ba8d-e3ca9f1edc1e
Hope ur problem is solved.
Pls award points for answers.

Debugging the webdynpro abap application from portal.

I developed a WebDynpro application and integrated in portal. I have to catch some portal events.For that i have written some code in my application. I tried to debug the application from portal by using all the available break-point types.but we could not .
Anybody have an idea how to debug a WebDynpro application from portal.
Thanks,
Kumar.

Hi
Few links to check:
External debugging is not working
Re: Debugging Abap webdynpro appln
Re: Unable to Debug WD ABAP application
Dedug is not working in Production Server.
a) Check on number of R/3 sessions opened at a time.
b) Check that user ID configured in portal using System Mapping Under 'Delegate User Administration' is the same user for which you are setting external breakpoint in backend system.

Debugging a webdynpro app

How to debug a webdynpro application.how to set break point in it?

Hi,
you can do it like in other abap programs,
set external breakpoint in your active coding (with the stop sign + person)
grtz,
Koen
**edit, read heidi's document for the complete info
Message was edited by:
Koen Labie

How to Debug WebDynpro-ABAP application

Hello Friends,
     1. How to Debug WebDynpro-ABAP application.
     2. What is modal dialog
     3. If Component contains more than one view, how to make one view is the default. Is that any way I can hide a view.
    4. Is that Component is the highest in the design structure, or any other types available like development components in WebDynpro-Java.
Thanx for Ur time.
Cheers,
Sam

Hi,
As i explained LIMU are subobjects like views as they dont have the seperate identity in repository so they have to be linked thru there parent component.
So when you transport whole component u can see there would be some entries in your transport list as LIMU types ( for views , windows).
OTR are text elements which u create for the elements of your view so u dont require to hardcode the text to be displayed as they need to be displayed in different languages so what you do is you create say button and for text to be displayed you create on OTR element under some package. now you give this package to your translation team to do all needed translations.
Yes DDIC types are from dictionary only but when you transport them so all newly created DDIC should also be transported.
P.S -> Pleas close this thread if satisfied with all questions.
Thanks
Anuj

How to debug program or Badi in SRM 7.0 through PORTAL

Hi friends,
        My question is How to debug a Badi or any program in SRM 7.0 through PORTAL . I putted External break point in Badi and following settings has been done in Utilities u2013 Settings u2013 Abap Editor
Front-End Editor (new) - checked
In debugging tab
Users - maintained (entered same user name using in Portal as log on user name)
IP Matching u2013 checked
ABAP Debugger u2013 New debugger u2013 checked
Session breakpoint active immed. - Chcecked
I am not able to debug this badi through Portal and some time after I am getting Time out error whereas Time limit is extended up to 600 seconds . In SRM 5.0 it is working fine .I have SAP ALL authorization   if any other procedure is available or for that any specific role needed then please share with me.
Regards,
Abhijeet
Edited by: abhijeet panse on Jun 29, 2010 8:02 AM

Hi ,
         Thanks Iftekhar and Yramki for replying. I checked everything and we have only one server for Development but still I am not able to debug, I checked AL08, it is showing same server we donu2019t have different application server for development. I donu2019t have any idea about that How to activate debugger for specific user id, please suggest me.
         Parameter set with value rdisp/tpda_for_ext = 1 . In the BADI i putted one infinite loop and then try to debug from the SM50 through Menu program/session u2013 Program u2013 Debugging but from GUI new debugger session is not opening and some time after process has been deleted from the SM50 and I got error message in the Portal.
         Do I need or missing some setting in Portal . Please suggest me.
Regards,
Abhijeet

How to create portal user and integrate with external appl login

How to create portal user and integrate the user with external application for single sign-on ?
I want to access my external application thru portal user ..?
Shyam

Hi Jithin,
The link that you've shared talks about a different scenario.
In my case, I want to pass the portal user id when the user clicks on the Help Link present in the header area.
I am trying to pass it along with the Help Link Url property of a masthead iview but it is not getting passed to the target Url.
I would like to know if it is possible to pass the Portal User Id in this way or not.
Though if we create a appintegrator iview and pass the user id <User.UserID> along with the target Url, it reaches there.
Thanks & Regards,
Anurag

How can I debug portal application?

What is the best IDE for developing portal application? So this IDE allows to debug
portal programs. Because a portal application is enterprise application, EJB will
possibly be used as business components. What IDE allows to not only degug components
that are reside in web container such as JSP and InputProcessor components but
also debug pipeline components that are reside in Enterprise Java Bean (EJB) container.
Many thanks!
Penny

My suggestion is to learn and use a logging framework in your enterprise
applications instead of relying on a debugger. (we use log4j and the
jakarta log tag library). This will also make maintenance and support of
your application much easier. It also is very usefull after deployment,
allowing you to configure it on the fly.
We like intellij very much (I think they have a sale on their personal
licenses going $200/each). Not for debugging, which it can do, but for ant
integration and its huge EJB and web application support. It can do things
like code completion and refactoring even in JSP pages. It is the only IDE
I've found that is very powerful but also gets out of your way and doesn't
impose its standards on your project.
Of course, when you ask for the best IDE you'll get many opinions.
"Penny" <[email protected]> wrote in message
news:[email protected]..
>
What is the best IDE for developing portal application? So this IDE allowsto debug
portal programs. Because a portal application is enterprise application,EJB will
possibly be used as business components. What IDE allows to not only degugcomponents
that are reside in web container such as JSP and InputProcessor componentsbut
also debug pipeline components that are reside in Enterprise Java Bean(EJB) container.
>
Many thanks!
Penny

How to debug in SAP Netweaver Developers Studio?

Hi there,
I am trying to debug and slove my error in SAP NWDS.
I am building portal application->JSPDynPage
I am trying to debug the jsp code behind page, it doesn't realli give error message like the java beans does.
I am quite new to this and do not know how to set the function to test and debug this page can anyone provide any solution ?
I have have this prob pls refer to this link
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=192104">https://www.sdn.sap.com/irj/sdn/thread?threadID=192104</a>
Thanks loads
Quatre

Hi Quatre ,
-Select the breakpoints in your Dynpages /beans in ur project
-To debug u have to change the prespective to debug which u can find in
window/open prespective /Debug in NWDS
-Select the Run/Debug or the Debug icon in the toolbar.
-Fill the project name ,application name in the in the wizard opnend .
- Follow the debugging using the next step over F6 ,step return F7 keys .
These link may be helpful:
http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/def86ab54da5418a3575373934ca00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/31e24044b80b06e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/cffcb407c67842b122bd1296dc810f/frameset.htm
U can always find out the way in the PDK development /how to debug/
ie in NWDS /HELP /SAP WAS AS Documentation /SAP J2ee Enterprise Java Beans/Java development User Guide /Running and Debugging
Cheers,
Swathi Rao
Do offer pts:-)

Error while configuring Debugging for WebDynpro Application

Hi Experts,
I am trying to configure Portal server for debugging a WebDynpro application.
In NWDS , in Debug configuration
When i tried to add my Webdynpro Project and application under Debug tab , No problem.
But when i checked J2EE Engine tab : it showed the following error.
<b>[J2EE Engine]: the selected server node does not run in restricted load balancing mode, please configure it correctly so that the URL extention can be used</b>
And ignoring it when i started debugging the application , the URL was formed like this :
http://<host>:50000/@@@DEBUG@@@7672950/webdynpro/dispatcher
/local/WDtest/WDtest?SAPtestId=1
with the error : The requested resource does not exist.
Details: Go to main page of this application!
Can anybody help me to fix the configuration.
Regards,
Ashish Shah

Hi,
To configure to the debugging mode... follow the steps:
1. Select "SDM" from J2EE engine (To get this view navigate thru Window--> Show View --> J2EE Engine)
2. Make a right click on "SDM" and choose "Enabling Debugging of Process"
3. Now, Navigate to Run --> Debug --> Select your Project as "Webdynpro Application" and click "new" button
4. Now give some name and Click BROWSE to select ur project and then click APPLY and DEBUG
Or if u use 2004s, then u can do the settings in Portal itself...which gives u more clear information... follow the link
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0cb32c5-36a7-2910-2c9b-ba4a5bbdbb56">WebDynpro Java Debug Configurator</a>
Hope it helps...
Regards / Guru

ABAP(R3) call to Portal(Webdynpro)

Hi experts,
I have a requirement to initiate a call from an ABAP program on R3 to a standard Portal (Webdynpro) API. Does anyone have any experience with this?
I understand that normally Portal (Webdynpro) applications will make the RFC call to ABAP via the established JCO connection. However there's very limited literature elaborating how the call can be made in the other direction i.e. from ABAP R3 to Portal
Anyone, please kindly advise how, if this can be done. Many thanks!
Best regards,
Lionel

please check the following link
http://help.sap.com/saphelp_nw04s/helpdata/en/da/f96f4132f15c58e10000000a1550b0/frameset.htm
with regards
shanto aloor

How to attach a WebDynpro Adobe form to backend Business Object?

Hello,
I would like to know if anyone has created an Interactive Adobe Form, and then after the user has filled it out (online, via WebDynpro view), attach the pdf form to an SAP Document, for example, Order, Purchase Order or Contract?
I know how to create the WebDynpro Interactive Form, and I then have the pdf object in context attribute of WebDynpro. But am not sure how to do the next step of taking that pdf and attaching it to the SAP Document.
Any suggestions or code samples would be greatly appreciated.
Thanks,
Colleen

The interactiveForm UI element has one action called onSubmit. This action is triggered when any server event occurs within the Adobe Form itself. So if you place a submitButton from the Web Dynpro Native (assuming you are using ZCI forms) within the form, it will automatically trigger the onSubmit action and WD event handler.
Here is a video that shows the process - although it is a little bit older and uses ACFx forms. You would want to use the new ZCI form approach. The general process for linking the events is the same however.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/c766e918-0b01-0010-99b1-c2b78cd059b3

Debugging abap webdynpro application

hi gurus,
an abap webdynpro application is runninf fine in developmernt server but not in production system. i transported the application again to refresh the application in production. but still the error persists. now i want to debug the abap editor in production system. so i wrote code 'BREAK POINT' in abap editor. but program is not stopping at this code. in dev as well as in prod system. please suggest.
Moderator Message: There is a separate forum for Webdypro for ABAP. Please post your question there.
Edited by: kishan P on Nov 29, 2010 1:25 PM

Hi
Few links to check:
External debugging is not working
Re: Debugging Abap webdynpro appln
Re: Unable to Debug WD ABAP application
Dedug is not working in Production Server.
a) Check on number of R/3 sessions opened at a time.
b) Check that user ID configured in portal using System Mapping Under 'Delegate User Administration' is the same user for which you are setting external breakpoint in backend system.

SPNego - Windows integrated Single-Sign On not working - How to debug?

Dear board,
I've tried to configure SPNego - Windows Integrated SSO with no sucess yet. We do use SAP EP7 on Windows Server 2003 64bit with MS AD 2003. The following is done:
- Service Account is created, authentication works when done on pupose
- SPNego wizard completed sucessfully, WebAs Java restarted
- IE6: Windows integrated Logon is activated, IE shows Intranet when accessing the portal url ( I can't modify the IE Security Settings yet, but as we do use KERBEROS outside of SAP as well, my assumption was settings are fine)
- UID in windows, EP and ECC are equal
When I access the portal URL, I am prompted for used id and password. How can I trace methodically what is wrong? Some kind of checklist with links, url or SAP Notes would be great. I've also read references to a test application as well as some diag / trace tool.
Please post thoroughly as I am rather new to this topic and still missing important terms and knowledge.
Kind regards and thanks in advance,
Richard

Dear board,
after the service principal name registration was done (once again maybe) the error message disappeared in the SPNego wizard when I retrieve the Principal in Step 2, the test resolution works as before in step 3 of the wizard.
At the moment, the error message in the central log file is still unchanged. Acquiring crendetials for realm xxx.xxx.org failed, no valid credentials provided.
#1.5 #001A4BAF485A0079000000040000207000043C8446E8BA7E#1192438730203#com.sap.engine.services.security.authentication.logincontext#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#J2EE_GUEST#0####d8ce7ab07afc11dc8d93001a4baf485a#Thread[Thread-307,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Security/Authentication#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: com.sun.security.jgss.accept
Login Module Flag Initialize Login Commit Abort Details
1. com.sun.security.auth.module.Krb5LoginModule OPTIONAL ok exception false null#
#1.5 #001A4BAF485A00580000007F0000207000043C8446E8C109#1192438730203#com.sap.engine.services.security.authentication.loginmodule.spnego.SPNegoLoginModule#sap.com/irj#com.sap.engine.services.security.authentication.loginmodule.spnego.SPNegoLoginModule#J2EE_GUEST#0####d8ce7ab17afc11dc8f50001a4baf485a#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Java###Acquiring credentials for realm XXX.XXX.ORG failed
[EXCEPTION]
#1#GSSException: No valid credentials provided (Mechanism level: Attempt to obtain new ACCEPT credentials failed!)
Any ideas? I haven't used the diag tool yet, is there any other reasonable way how to debug the setup?
Kind regards and many thanks,
Richard

How to debug portal webdynpro appl

Similar Messages

Maybe you are looking for