Web dynpro name in portal

Hi,
How can i find the names of the Web Dynpro components that are being called through standard iviews in portal. For instance if I want  to see that which web dynpro component is attached to standard iview Employee Search then where will I find this Information. When I see the property of this Iview then in the
application name it says:  XssMenuArea     &
application namespace : sap.com/pcui_gp~xssutils
So what is the exact name of the webdynpro application that is being called here which i can see in SE80.

Hi,
The application name and namespace what ever you have mentioned is Webdynpro for JAVA.
You can find the name of the component used in the application under the below navigation.
Content Administrator -> WebDynpro -> Deployed Content
under the deployed content you will find all the namespaces that are available in your portal. Definitely you will find the standard SAP namespace "sap.com". if you search in that list, you will easily get the application what you are looking for. Expand the menu and you can find the component used for the application you have mentioned.
Thanks,
Mahendran B.

Similar Messages

  • Not able to run web dynpro application from portal.

    Hi portal experts,
    I want to run my web dynpro application from portal.
    So created a seperate iview  and a role  for the purpose.
    Assigned the iview to the role and also mapped a abap user id to the new role created.
    But when I click on 'preview'  the iview , getting the following dump.
    Error when processing your request
    What has happened?
    The URL http://mnghcmsap:8000/sap/bc/webdynpro/sap/zhr_cp_admin/ was not called due to an error.
    Note
    The following error text was processed in the system HRM : Die URL enthält keine vollständige Domainangabe (mnghcmsap statt mnghcmsap.<domain>.<ext>).
    The error occurred on the application server mnghcmsap_HRM_00 and in the work process 0 .
    The termination type was: RABAX_STATE
    The ABAP call stack was:
    Method: CHECK of program CX_FQDN=======================CP
    Method: STARTUP_CHECKS of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
    Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
    Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
    Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
    Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
    Module: %_HTTP_START of program SAPMHTTP
    What can I do?
    If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system HRM in transaction ST22.
    If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server mnghcmsap_HRM_00 in transaction SM21.
    If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server mnghcmsap_HRM_00 . In some situations, you may also need to analyze the trace files of other work processes.
    If you do not yet have a user ID, contact your system administrator.
    Error code: ICF-IE-http -c: 200 -u: INF51515 -l: E -s: HRM -i: mnghcmsap_HRM_00 -w: 0 -d: 20110209 -t: 121224 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
    HTTP 500 - Internal Server Error
    Your SAP Internet Communication Framework Team
    Please let me know if I am doing the process correctly and also let me know if I am missing somthing.
    Thanks,
    Aditya.

    Are you able to run teh web dynpro application independtly i.e. without creatin an iview.
    http://mnghcmsap:8000/sap/bc/webdynpro/sap/zhr_cp_admin/ by using this link.
    or there also you are getting the error.
    i guess there also you should be gettign the error.
    this is some problem with the FQDN settings in the abap system.
    in the host name of the web dynpro applciation server one .(dot) is must.
    so you might have to change the host name to some thing like mnghcmsap. from mnghcmsap
    thanks
    sarbjeet singh

  • Prob. exec. print job from RFC which im calling Web Dynpro java in Portal

    Hi,
    Ive got a problem executing a print job from an RFC which im calling in Java web Dynpro Application in Portal. Im using an Acess Method G: for Front End Printing but Order gets stuck with the Status "Waiting" "Front end unavailable".
    Any help would be greatly appreciated.
    Thanks in advance!!!

    HI,
    I dont think you would be able to do this. Instead, you need to get the content from RFC into WD java and print from the browser.
    Regards
    Srini
    Edited by: Sinivasan Rajamani on Jun 14, 2010 4:25 AM

  • Passing a parameter while calling a web dynpro application on portal

    hi
    I am having a web dynpro application which retrieves data from R/3 system via RFC using Jco destinations define in the Portal.
    Now we have different kinds of portals running on the same WAS, now I want the application to run which access data from different R/3 systems thru different JCo destinations.
    I need to create a logic such that mu application runs fine on any portal with any Jco destination.
    Is there any provision to achieve this.
    kindly let me know about this.
    Thanks and regards
    kris

    Gopi,
    there's an parameter called "sap-wd-arfc-useSys" you can pass to the application, to change the used JCo-Connection (read more at http://help.sap.com/saphelp_erp2005/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm)
    so, if you're running the WD-aaplication on <b>one</b> WAS and call it from different portals, you have to create three (or six with the META-connections) JCo-Connection on your WD-WAS.
    In a WD-application you can access URL-Parameters with:
    WDWebContextAdapter.getWebContextAdapter().getRequestParameter("<your URL Parameter-Name>");
    kr, achim

  • Web dynpro using a portal service

    Hello All,
    We are using the JDI.
    We want to use a portal service DC from a web dynpro DC.
    The web dynpro DC is part of a software component.
    When the portal service is a local DC it is working fine (except failing later on the CBS build)
    but when the service is part of a software component as well I get a runtime exception: a java.lang.NullPointerException.
    The WD sharing reference I'm using is: PORTAL:sap.com/<dc service prefix>.<service name>
    I assume that this is the right reference because without this exact phrase I get a java.lang.NoClassDefFoundError: com/sap/<name of service>
    <b>Does anybody know how to use a portal service that is part of software component?</b>
    Thanks a lot in advance, Adi.

    Thanks Bharathwaj , but I already solved my problem.
    The solution was  to change the next code line in the service client code :
    Idb_srv DB_Service = (Idb_srv) WDPortalUtils.getServiceReference(Idb_srv.KEY)
    to:
    Idb_srv DB_Service = (Idb_srv) WDPortalUtils.getServiceReference(""<PARFilename>.<service name>");
    Regards, Adi.

  • Problem with integrating Web Dynpro into anonymous Portal

    The problem is that we can't run the Web Dynpro application in combination with an anonymous portal.
    <b>We get the following error:</b>
    Runtime error portaal
    Fout opgetreden bij verwerking opdracht voor :
    iView : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
    Naam component : com.sap.portal.appintegrator.sap.WebDynpro
    Exception in SAP Application Integrator occured: ApplicationIntegratorException.
    Exception id: 02:31_29/10/07_0168_426375450
    See the details for the exception ID in the log file
    <b>Detail description of the situation:</b>
    At one of our companies we are using a Portal in combination with a Web Dynpro application. The portal is for internal use only so therefore we are using a language specific anonymous user (/irj/portal/anonymous?guest_user=Guest_intra_NL). The Web Dynpro application needs no authentication either. The Web Dynpro applications runs inside an appintegrator iView somewhere on the frontpage. If we set the authentication schema on 'default' instead of 'anonymous' we have to authenticate (inside the iView only). If we authenticate then the Web Dynpro application works fine. So only in combination with a anonymous user the application is not working.
    <b>We performed all these settings:</b>
    Anonymous user access to Web Dynpro
    <b>This is a small part of the trace file:</b>
    Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : Guest_intra_NL
    at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
    at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
    at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
    at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
    at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
    at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
    at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
    at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
    at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
    ... 29 more
    #1.5 #00144F790FF0005D00000D8500000D5500043D60120F2656#1193382735975#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Content pass of Application Integrator failed.
    Component Name:       'com.sap.portal.appintegrator.sap.WebDynpro',
    Context Name (iView): 'pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4',
    Top Layer:            'WebDynpro/TopLayer',
    Producer ID (FPN):    'null',
    System Alias:         'SAP_LocalSystem',
    [EXCEPTION]
    #1#com.sapportals.portal.appintegrator.ApplicationIntegratorException: ApplicationIntegratorException
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:96)
         at com.sapportals.portal.appintegrator.accessor.system.SAP_LocalSystemAccessor.getAuthenticationData(SAP_LocalSystemAccessor.java:83)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.AbstractAuthenticationMethod.getUserCredentials(AbstractAuthenticationMethod.java:54)
         at com.sapportals.portal.appintegrator.layer.authenticationmethod.SAPLogonTicket.computeAuthentication(SAPLogonTicket.java:31)
         at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:45)
         at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:159)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doActionPass(AbstractIntegratorComponent.java:68)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:54)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:368)
         at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:799)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:652)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.security.api.umap.NoLogonDataAvailableException: No logon ticket available.
         at com.sap.security.core.umap.imp.UserMappingDataImp.getAuthenticationTicket(UserMappingDataImp.java:1772)
         at com.sap.security.core.umap.imp.UserMappingDataImp.enrich(UserMappingDataImp.java:351)
         at com.sapportals.portal.appintegrator.accessor.ume.UMEAccessor.getTicket(UMEAccessor.java:91)
         ... 33 more
    #1.5 #00144F790FF0005D00000D8700000D5500043D60120F3B56#1193382735981#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#0####c817f770839211dc850f00144f790ff0#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java###Exception ID:09:12_26/10/07_0701_426375450
    [EXCEPTION]
    #1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.spe.spe_intranet/content/sites/nullAtSPE2/Connecting/nullAtSPE/AtSPE/Random4
    Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
    User : Guest_intra_NL
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: ApplicationIntegratorException
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:123)
         at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
         ... 29 more
    Hopefully someone has any clues. Thanks in advance. Of course will I reward points for the solution.
    Grtz, JM

    Hi Kelly,
    the point here is native SharePoint integration. If your company does not have a SharePoint strategy then I absolutely agree with you. There are plenty of ways on how you can integrate WebDynpros, iViews, and other "SAP views" in SharePoint.
    The "problem" with these integrations is always that it is not a native / low-level integration. It is just an iFrame within SharePoint that contains data coming from another system. This means that this data is isolated from any other functionality that is available in SharePoint.
    Of course this can be enough for some usecases (maybe for all of yours ), but there are lots of companies who do want to leverage all of SharePoints (collaborative) functionalities. In this case Duet Enterprise does offer a way to integrate SAP objects into SharePoint on a "low-level". All objects that are integrated into SharePoint are then available as "real" SharePoint objects. You can work with them like with any other SharePoint object. You can even offline them using standard SharePoint functionalities. You can bring them to Outlook without any major development, ...
    All this because we not only include an isolated iFrame in SharePoint, but really integrate the data.
    Like I said: there are certainly usecases where this is not required and a simple iFrame is all that you need. However, we have seen in several projects now that there is also a requirement / need for a "deeper" integration.
    Regards,
    Holger.

  • When to use WEb Dynpro application and Portal application in NW dev studio

    I would like to know what is the difference between
    webdynpro application  and EP Application using PDK.
    Are they comaparable  ...Which one has an edge over the other specific to any applications.
    I want develop an application related to e-commerce using the SAP R3 as backend for an industiry(where in a registered user can place an order and query on the staus of order. All the data will be stored in R3 ).
    I am planning to dev this using NW dev studio , but have an appehension about which application is useful for this kind of application either webdynpro or EP application .
    can anybody explain which one has edge over the other ( Webdynpro or EP applcations in context with NW Dev studio) and why.
    thanks
    PK

    Hi,
    <b>Webdynpro</b> is used when requirements ask for a prototype using minimal time n effort.
    Highly skilled programmers are not necessary to write a webdynpro application
    It uses dynamic controls without reloading the page.
    <b>Portal components</b> esp Abstract portal component provides a lean method to write HTML command to web client
    Large interactive components requires more programming.
    <b>WebDynpro</b> is a highly declarative, tool-based programming model. It minimizes platform-dependent "plumbing" code for building UIs and maximizes declarative metadata describing huge portions of a typical application in a platform-independent way.
    Web Dynpro follows a "top-down" approach in order to consistently support multiple runtime platforms.
    In Web Dynpro you just have to drag & drop the UI components.
    <b>Portal components</b> has followed a "bottom-up", programming-driven approach to Web development.
    Regards,
    Pooja.

  • Web Dynpro Java - Light Portal Desktop

    Hi Guys... I have a web dynpro java application that I want to display on a Light Portal Desktop, but when I display the iview... it gets cut. I mean I can see only part of my application and there is also a right scroll bar... It looks like the height size of the iview is set to "FIXED" but it's not. I Actually  modifed all values for size even on the Light Framework Page used...to FULL_SCREEN. I don't know what's wrong. If I display the same iview using a Default Framework Page it looks fine... I'm using SAP EP 7.00 SP 16.
    Is there any restriction for using Web Dynpro iviews for Light Porta Desktops?
    Thank you.
    David

    David,
    Webdynpro content is considered heavy and I dont think we can use it in LPD.
    Update:
    Note 916545 - Central Note for External-Facing Portal (NW 7.0)
    Check under application.
    Regards,
    Sandeep Tudumu
    Edited by: Sandeep Tudumu on Sep 17, 2008 8:56 PM

  • Web Dynpro ABAP Stylesheet - Portal Integration

    We have a Web Dynpro ABAP being displayed through a Portal iView.  The Portal server and the Web Dynpro ABAP server are separate.  Our problem is in getting the Web Dynpro ABAP to use the stylesheet of the Portal.
    We can make this work by forcing an external stylesheet (via application parameters, global Dynpro settings, or passed on the end of the URL), but we have to hard-code the full URI of the Portal stylesheet.  This would be very hard to manage if we hard-code every iView's CSS location (or set every individual Web Dynpro's application parameters), and we want instead for the Portal to supply whatever the user's stylesheet is dynamically. 
    So what we want is: if we change the Portal stylesheet, the Portal would just pass the new stylesheet URI to our ABAP Web Dynpro iViews without manual modification of the iViews.
    Here is an example of what works:
    http://our-abap-server.com/sap/bc/webdynpro/sap/cprojects?sap-ep-themeroot=https://our-portal-server.com/irj/portalapps/com.sap.portal.design.portaldesigndata/themes/portal/ourportalstylesheetname
    Shouldn't the Portal iView automatically pass sap-cssurl or sap-ep-themeroot to Web Dynpro ABAP?  We have "Supply Portal Stylesheet" checked on the iView… it just doesn't pass anything to the Web Dynpro ABAP.  Why wouldn't SAP pass this parameter dynamically to the Web Dynpro ABAPs?  Is this a product error? 
    There seems to be a great deal of confusion about this on the SDN message forums... I think this may be the core issue.
    We are using a 7.0 SP13 Portal with an ECC 6.0 SP12 backend.

    Now that you mention it, I ran into that exact same issue  -- the application parameters didn't work for hard-coding the theme.  The fix ended up being the web server semicolon thing I mentioned earlier (that was why the parameter didn't make it to the backend). 
    The themeroot is automatically sent to the backend from the portal, so you shouldn't really have to manually send it as a parameter anyways.
    I'd suggest talking to your network guys.  Also this could be the result of the SP you are on (we're on 13 for the portal and the backend system -- maybe this feature doesn't work in some earlier SP's?).  There are also some options to force the theme as a WD application parameter on the backend side, which you could check into.  Details on those are here:
    [http://help.sap.com/saphelp_nw2004s/helpdata/en/7b/fb57412df8091de10000000a155106/frameset.htm]
    Also you could look at the requests being made by installing HttpAnalyzer in your browser.  You can inspect "post" parameters going from the portal to the backend system.  One of those posts (the first one to the backend system) should contain the parameter sap-cssurl (same kind of thing as sp-ep-themeroot).  This is where our problem turned up as this parameter was not being posted.
    Lastly, make sure that your frontend portal and backend portal are in the same domain.  For instance:
    frontend.domain.com
    backend.domain.com
    If your backend and frontend are in different domains it messes all kinds of things up, including stylesheets I think.  If you can't get around this, then read about domain relaxing (but I highly recommend getting the domains the same).
    When we started, ours were:
    portal.dx.company.com
    sap.company.com
    This created all kinds of problems.  Putting our systems in the same domain with the same protocol and fixing our little semicolon web server problem fixed basically all of our portal complaints.  Up until that time, we had also had many problems with session management (backend sessions were getting stuck until the HTTP timeout).
    That's all I know.   Good luck.

  • Accessing Web Dynpro application outside portal

    Hello alles,
    Our customer wants to display a Web Dynpro application result on a regular hmtl intranet page, i.e. without showing the portal.
    We have tried with html frames, but end up with a flickering or empty screen. The problem occurs both with a quick link to the application within the portal, an SSO link, a link to the iView, a webdynpro/dispatcher address ...
    It seems as if the problem occurs with all WD iViews, but not with e.g. a regular News iView.
    Do you have any suggestion on how we could solve this? Reasons?
    Thank you in advance!
    Brgds,
    Caroline
    Message was edited by:
            Caroline Janzon

    hi
    good
    go through this link,hope this ll help you to solve your problem
    http://www.sap-press.de/download/dateien/1103/sappress_maximizing_web_dynpro_for_java.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/wd%20java/wd%20tutorials/using%20ejbs%20in%20web%20dynpro%20applications.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b5380089-0c01-0010-22ae-bd9fa40ddc62
    thanks
    mrutyun^

  • Calling a web dynpro application via portal using SSO

    Hello Expert,
    i have a requirement where i need to call a web dnpro application via portal.
    But it is asking for user name and password.
    i want to call using single sign on.
    Can u please suggest a way.
    i did the coding like this:-
    CALL METHOD cl_wd_utilities=>construct_wd_url
    EXPORTING
    application_name = l_c_appl_name
    IMPORTING
    out_absolute_url = l_v_gv_url_string.
    l_v_icf_url = l_c_icf_url_val.                      "#EC SYNTCHAR
    CALL METHOD cl_icf_tree=>if_icf_tree~service_from_url
    EXPORTING
    url             = l_v_icf_url
    hostnumber      = l_c_0
    authority_check = space
    IMPORTING
    icfactive       = l_v_m_sso_active.
    IF l_v_m_sso_active = l_c_x .
    CREATE OBJECT o_viewer
    EXPORTING
    parent = o_empty_co.
    CALL METHOD o_viewer->enable_sapsso
    EXPORTING
    enabled = l_c_x
    EXCEPTIONS
    OTHERS  = 0.
    l_v_gv_url_c = l_v_gv_url_string .
    CONCATENATE l_v_gv_url_c l_c_url_string p0022-pernr INTO l_v_gv_url_c.
    CALL METHOD o_viewer->detach_url_in_browser
    EXPORTING
    url        = l_v_gv_url_c
    EXCEPTIONS
    cntl_error = 1
    OTHERS     = 2.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
    RAISING error_occured.
    ENDIF.
    cl_gui_cfw=>flush( ).
    ENDIF.
    but it is not working
    thanks
    Mahesh

    Hi Mahesh,
    You need to setup a Single Sign On between SAP Portal and ECC system where yoy are doing the development.
    Ask basis team to setup the single sign on and usually this is the job done by Basis teams. Refer the below link to get some idea on SSO setup:
    http://scn.sap.com/community/enterprise-portal/blog/2013/12/15/sso-configuration-between-sap-portal-73-and-ecc-60-ehp-6
    Thanks
    Krishna

  • Storing user defaults of Web Dynpro application on portal

    Hi folks,
    I am trying to develop Web Dynpro application that runs in an iView on a portal. I would like to remember certain user defaults for this application (e.g., user default plant). User also has control over this value, so whenever they change it, the value should be update on a backend as well.
    My first thought was to use PCD, but I am not sure how to do that - all the code examples for I found for PCD looked like they were created for portal application, not Web Dynpro ones.
    Anybody here actually done anything similar?
    Edited by: Alexei Isaev on Jan 29, 2008 8:20 PM

    Hi Alexei,
    If you need to store default values for a portal application, you may consider your development in Web Dynpro for ABAP.  I have not come across application level personalisation yet in Web Dynpro for Java, unless someone else can throw some light here.
    Regards,
    Subramanian V.

  • DB access in Web Dynpro application in Portal

    Hi,
    I will develop a web dynpro application which will run in the EP and use an DB. How are the best practices in this scenario ? Should I use a Web Dynpro Model (EJB or WebService) for the persistence operations or should I use Portal Services ?
    Regards
    Flo

    Hi Florian,
    go trrough these docs:
    EJBs in Web Dynpro Application Using Wrapper Class
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00be903b-8551-2b10-c28a-8520400c6451]
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c]
    Accessing database table using EJB and web dynpro
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70929198-0d36-2b10-04b8-84d90fa3df9c]
    Oracle Connectivity with EJB using WebDynpro Application
    [https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdjava/oracle%2bconnectivity%2bwith%2bejb%2busing%2bwebdynpro%2bapplication]
    [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0b657b7e-0c01-0010-74a4-b71518871800]
    hpe it hlps u...
    Regards
    Khushboo

  • Deploy Java Web Dynpro to the portal

    Hi Gurus,
    I've done a simple java web dynpro in my local PC. How do I deploy it to the portal? Thanks!
    Best regards,
    Anthony

    Hi,
    Please go through this article to know how to deploy webdynpro applications in the portal
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/40d983b4-bfc2-2b10-858f-b717e194f2c1
    Regards,
    Gayathri

  • Navigate from Web Dynpro app to portal page

    Dear All,
    I've created a number of Web Dynpro applications which I run from various portal pages. From one of the Web Dynpro's I navigate to a different portal page using the WDPortalNavigation.navigateAbsolute method. This works fine, but I'm left with one problem:
    I'd like to pass parameters from the Web Dynpro which navigates to the portal page to the Web Dynpro applications which run on that specific page. I've appended the parameters to the URL I'm navigating to (eg ROLES://<pcd location>?<param=xxx>) and in the Web Dynpro's I've added a parameter to the Default interface plug. This doesn't seem to work. As an alternative I've added the statement WDWebContextAdapter.getWebContextAdapter().getRequestParameter("param") to the doInit() method of the view, but this also doesn't work.
    Either I'm doing something wrong, or what I want to accomplish is not possible. Does anybody know of a way to access parameters passed to a portal page from Web Dynpro applications contained on that page?
    Thanks,
    Arnoud

    I hope you are passing parameters between two WebDynpro applications.
    Please go through the example available for passing interaction between two webdynpro components.
    Please check the following link
    Alternative method for navigating to another page ?
    or the following link
    Re: Can we pass parameters in querystring of the webdynpro application?

Maybe you are looking for

  • PGI error after delivery and picking completion

    Dear gurus, I have a problem as mentioned below For a meterial delivery and picking has been successfully completed. while go for PGI, " the 0 qty available for the material message is showing ". Please provide the solution to how to check and contin

  • Printing of data in duplex mode

    Hi Friends               I am having some problem working with smartforms. I have desined two pages. 1. page1 with main window 2. PAGE 2 for terms and conditons. I have to print data such that terms and conditions on every page backside. Problems is:

  • Java not working in browser

    Hi there! A couple of weeks ago, I started having trouble with Java functions, such as drop-down menus and popups. Most of the time, they simply don't work. I haven't changed anything on my computer, so I don't know what is causing the trouble. I did

  • Index Creation Error, while creating Information space

    Hi, I'm trying to create an Information Space in explorer based off of a Universe created on a Bex Query from SAP BW.  This Universe is created in Universe design tool based on BW 7.4,  gives below error, while creating report in  Web Intelligence ba

  • Jukebox Zen Xtra in Rescue M

    Well, it happened.... I dropped my Nomad Jukebox Zen Xtra today. When I turned it off and turned it on again, it went into rescue mode and is offering me 4 options: . Clean Up 2. Format All 3. Reload OS 4. Reboot I have tried reboot but it returns to