Assigning a login module to a Web Dynpro application

Hi everybody,
I would like a Web Dynpro application to use a custom login module for authentication. How can I do this?
What I found is the Security Provider (in the Visual Administrator tool) where I can add a login module to the "form" authentication mechanism for example. But if I do this I think all applications using this mechanism have to use my custom login module, right?
I wonder if I have to add my Web Dynpro application as a component to the Security Provider so that I can assign login modules to it. Am I on the right way? If yes, how can I do this? If I choose "Add" from the "Policy Configurations" tab a popup appears where I can enter the name for a new component. How do I specify my application there?
Thanks in advance for all answers,
Torben

Hi,
Web Dynpro applications use the ticket authentication template. U wud need to add your login module to the ticket template's login stack.
Incase you are accessing the Web Dynpro applications thru the EP u wud need to make changes to the authschemes.xml file too.
regards,
Vishal

Similar Messages

  • How do you call a function module in a web dynpro application ?

    Why do you delete my postings ?????????????????????????????
    pls see subject
    Edited by: Ilhan Ertas on Apr 1, 2009 4:51 PM
    Edited by: Ilhan Ertas on Apr 1, 2009 4:52 PM

    Its not me deleting them.  Perhaps a different moderator or a technical problem within SCN itself.
    Someone might be concerned about your question because it is very basic.
    You can call a function module from WD the same way you did in any ABAP program - with the CALL FUNCTION syntax.  There is a service call wizard that will generate a matching context and calling code for you - but it is just a helper, code generator.  Everything it does can be done by hand as well (and often better than the generator).

  • Assigning a login module to a single WebDynpro to authenticate against LDAP

    Hi there,
    we are running the J2EE Engine 7.0 within XI on SAP NetWeaver 2004s / Linux x86_64.
    Basically, i want to Authenticate a Java WebDynpro against an LDAP (Active Directory). With the XI Usage installed, I can not customize the UME to authenticate against an LDAP (not supported and not possible).
    Thus, I want to use a custom login module or, if suitable, a standard login module to authenticate against LDAP. I know that all WebDynpro Apps use the default authentication scheme that in turn references the authentication template "ticket".
    1) Can I use a predefined Login Module to authenticate against Active Directory LDAP or do I have to write a custom login module?
    2) Is it possible to assign a login module to a single WebDynpro and how can I do this?
    Thanks a lot in advance,
    Oliver Kalkofen

    > Thus, I want to use a custom login module or, if
    > suitable, a standard login module to authenticate
    > against LDAP.
    We have developed a custom login module which does this. It looks to the user like the BasicPasswordLoginModule provided with SAP, but the userid and password entered has to be a valid accountpassword from the Active Director domain. We use the Kerberos protocol to perform this useridpassword validation, not LDAP. The userid can be just a name, in which case the default domain (realm in Kerberos terminology) or it can be specified as user@REALM in which case a non-default realm can be used to authenticate. Once the authentication is complete, we look in USRACL table to map this Kerberos principal name onto a SAP userid so we can then create an SSO2 ticket.
    If you interested to evaluate, or get a quote for purchasing this, please contact me offline. Of course, you can develop your own if you are happy to do so. I just thought you might be interested to know of an alternative.
    Thanks,
    Tim

  • Restrict simultaneous login to a web dynpro application by the same user

    I have a stand alone web dynpro application and used the sap.authentication for user to login into the application. How can i restrict a user from accessing the application from two different browsers using the same userid?

    Hi,
       You can try the following approach:
    1. Create an outbound plug to some dummy view which shows the message to the user that he/she is already logged in. Let's call this plug "ToMessageView".
    2. In the "wdDoInit" method of the component controller write the following code:
    String loggedInUserID = WDClientUser.getLoggedInClientUser().getClientUserID();
    String[] apps = WDServerState.getActualApplications(loggedInUserID);
    //All entries of apps will look like <application-name>/<application-id>
    boolean isRunningParallely = false;
    for (String app : apps) {
         if(app.split("/")[0].equals(wdComponentAPI.getApplication().getName())){
              isRunningParallely = true;
              break;
    if(isRunningParallely)
    //fire the plug to message view here
    FYI, I haven't tested this but do try it out.
    Regards,
    Satyajit

  • 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

  • Access users in a Web Dynpro application on different WAS ??????

    Hi,
    Scenario - I have a local WAS on which i have deployed a Web Dynpro Based application.
    There is another WAS on which I have portal installed. I need to access the roles assigned to a particular user in my Web Dynpro application.
    Query -
    I need to know can i access the roles assigned to a user on a different WAS in a Web Dynpro based application running on a different WAS.
    Thanks and Regards,
    Amol Ghodekar.

    Amol,
    as this questions existed twice, I've deleted one.
    As roles are in the UME, you can access them. But why do you want to do this? You could login to that user, but then the question is what you want to do....
    Regards,
    Benny

  • Securing Web-Dynpro application with Netegrity

    Hi,
    I'm developing a web-dynpro application that will be secured by Netegrity SiteMinder. SiteMinder is a reverse-proxy that authenticates the user and adds the user details as additional headers to the HTTP stream. According to the documentation I found in SDN with regards to JAAS and NetWeaver it looks like SAP has added callbacks so that I can retrieve HTTP headers in my custom login-module. I've implemented a simple login-module and deployed it, but now am stuck with the following issues:
    (1) I can't seem to be able to debug the module (even when I create a simple HelloWorld.jsp and require the use of this module in the visual administrator, the debugger seems to ignore the break-points).
    (2) I can't find any possibility to configure the engine so that this specific module is required for authenticating my deployed web-dynpro application.
    My questions are as follows:
    (1) Is it possible to use standard JAAS authentication with web-dynpro applications?
    (2) How do I debug JAAS login modules?
    Regards, Chris.

    <b><b>Hi Adrian
    During the Life cycle of your application Your connection will be Released when it is inactive for particular Time (The inactive time limit will be specified in the JCo Pool Settings that would be in milli seconds)
    The RFC Connection can be Monitored using the Gateway process .
    There are Some Predefined Connections in the Gatewway Process and each connection Requires approximately 200Kb of Memory.
    So the memory cosumption of the Gateway process is proportional to the number of Active RFC Connection.
    For More Details Check This
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/85a483cb-0d01-0010-2990-c5168f01ce8a">JCo Connection Pools</a>
    Regards
    Chandran S</b>

  • SDM failed when deploying a Web Dynpro application

    SDM failed when deploying a Web Dynpro application - I get the following error message:
    Sep 19, 2006 2:25:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [001]Deployment aborted
    Settings
    SDM host : eix-blade-011
    SDM port : 50118
    URL to deploy : file:/D:/DOCUME1/AMRM1.AZI/LOCALS1/Temp/temp43621sap.comwelcome.ear
    Deployment exception : Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011
    Inner exception was :
    Server eix-blade-011 did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server eix-blade-011 at port 50118: eix-blade-011

    Amr Azim,
    You must have logged in thru a dedicated connection to any server through say VPN before deploying.This way the sdm uses the same login as that of already establised connection.
    So 'sign of'  all connections to any servers before deploying and redeploy your application.Here you will be prompted to supply the sdm password and deployment shall proceed.

  • I am getting a error while executing the Web Dynpro Application Page.

    Hi All,
    I am getting a Error while executing a web dynpro application ::: 
    : Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component: Z_WEP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    I have checked this error description in ST22  :
    What happened?
        The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere
         along
        the call hierarchy.
        Since exceptions represent error situations and this error was not
        adequately responded to, the running ABAP program
         'CL_WDR_CLIENT_APPLICATION=====CP' has to be
        terminated.
    Error analysis
        An exception occurred which is explained in detail below.
        The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught
         and
        therefore caused a runtime error.
        The reason for the exception is:
        Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered. Component:
        Z_XXP_PERSONAL_DATA, View: OVERVIEW, Window: Z_XXP_PERSONAL_DATA
    Can u plz help me regarding this error.
    Thanks,
    Deepika

    >Navigation in Phase WDDOMODIFYVIEW Cannot Be Triggered
    Looks to me like you are trying to fire a navigation plug within WDDOMODIFYVIEW. According to the rules of the WD Phase Model this is not allowed.

  • Cannot deploy Web dynpro application from NWDS

    Hi,
    I am new to EP. I created a web dynpro application in nwds and tried to deploy it. But it gives the following error .
    Settings
    SDM host : nw04
    SDM port : 50118
    URL to deploy : file:/E:/WINDOWS/TEMP/temp12188WelcomeWebDynproprj.ear
    Result
    => deployment aborted : file:/E:/WINDOWS/TEMP/temp12188WelcomeWebDynproprj.ear
    Aborted: development component 'WelcomeWebDynproprj'/'local'/'LOKAL'/'0.2007.05.02.19.35.01'/'0':
    <b>Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool</b>. For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: Wrong security credentials detected while trying to obtain connection to the J2EE Engine.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    I have even configured J2EE server in the nwds through preferences. I have used the default passwords during installing sneak preview.
    What should i do to deploy my application  successfully??????

    My Server settings are fine in preferences of NWDS. Every thing is showing green
    I get the same problem even when i delpoy through SDM.
    This is the error when i deploy through SDM
    Deployment started Thu May 03 06:27:27 PDT 2007
    ===========================================================================
    Starting Deployment of MyFirstWebDynProPrj
    Aborted: development component 'MyFirstWebDynProPrj'/'local'/'LOKAL'/'0.2007.04.14.22.37.46'/'0':
    <b>Cannot login to the SAP J2EE Engine using user and password as provided in the Filesystem Secure Store. Enter valid login information in the Filesystem Secure Store using the SAP J2EE Engine Config Tool.</b> For more information, see SAP note 701654.
    com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthExceptionWrapper: <b>Wrong security credentials detected while trying to obtain connection to the J2EE Engine.</b>
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMAUTHEXC)
    Deployment of MyFirstWebDynProPrj finished with Error (Duration 6656 ms)
    It seems like a configuration issue in SAP J2EE Engine Config Tool.What should i do.
    Highest points will be awarded if some one can help me in this

  • Cannot deploy web dynpro applications

    Hello,
    I'm starting to develop web dynpro applications, and I can run them on the nwds, but I cannot deploy them to the SDM, i always get the following error:
    /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
    [003]Deployment aborted
    Settings
    SDM host : myserver
    SDM port : 50118
    URL to deploy : file:.../Temp/temp53918Welcome.ear
    Deployment exception : Server myserver did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server myserver at port 50118: No route to host: connect
    Inner exception was :
    Server myserver did not accept login request as admin on port 50118. Details: ERROR: Could not establish connection to server myserver at port 50118: No route to host: connect
    I have installed Sneak Preview SAP NetWeaver 2004S SR 1, i can access the  enterprise portal with no problems.
    I would be appreciate if anybody could help me with this issue.
    Regards,
    Leandro Fonseca

    At the same time if more users are deploying then you may such 'deployment aborted' errors check if there are more child instances for the J2EE engine.If not ask your basis administrator to create more child nodes to balance the load on the server instance.Also You can find out the server details at
    "http:
    <hostname:portnum>\index.html"select system configuration-you can get the details of the SDM and the j2ee engine from there.You need to have proper credentials to get the information from the above url.
    Provide those details in the NWDS.

  • Errors in While trying to Deopy Web Dynpro Application

    Hi,
      I have NetWeaver 2004S in My local System. I am facing one problem while deploying that Web Dynpro Application from NWDS. Error is pasted below. But i can deploy EP Application. I am facing the same problem when i tried to Deploy from Remote GUI.
      Can anyone help me in fixing this problem.
    Thanks,
    Sridhar
    <u>Exception i got while deploying.</u>
    Starting Deployment of SampleWD
    Aborted: development component 'SampleWD'/'local'/'LOKAL'/'0.2006.06.05.11.29.10':
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
    com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [H1B-2F241-HMY] with user name: [Administrator]                     Check your login information.                     Exception is: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Cannot authenticate the user.]
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.checkLoginCredentials.DMEXC)
    Deployment of SampleWD finished with Error (Duration 2473 ms)

    Hi Sridhar,
    Please follow the steps below:
    1. Open ConfigTool ( drive:\usr\sap\J2E (your instance)\JC01\j2ee\configtool
    2. Go to Secure Store and change the password for the property admin/password/J2E (This password should same as the one you are trying to login to portal)
    3. Click Add
    4. Click Save and restart your server.
    Should be able to deploy your components.
    Happy deploying
    Best Regards,
    Shiva

  • Error while running web dynpro application

    Hi Experts,
    I have a web dynpro application that is consuming web services from PI 7.1
    I have deployed the application on PI 7.1 server and created web service destination also.
    I have tested the web services and they are working fine.
    I am geting the following error when i am running the code,
    The initial exception that caused the request to fail, was:
    com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    Detailed Exception Chain
    Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'DEFAULT_WS_XYZ_METADATA_DEST' and WS interface ' XYZ_WSD_PI'. One possible reason is that the metadata destination 'DEFAULT_WS_XYZ_METADATA_DEST' has not been properly configured; check configuration.
    at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
    at com.dts.model.xyz.xyz.<init>(xyz.java:52)
    at com.dts.comp.DTCComp.wdDoInit(DTCComp.java:184)
    at com.dts.comp.wdp.InternalDTCComp.wdDoInit(InternalDTCComp.java:420)
    Caused by: com.sap.engine.services.webservices.espbase.configuration.ConfigurationMarshallerException: com.sap.engine.lib.xml.util.NestedException: -> com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    at com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions_WSPOLICY_12_NS(SecurityConfigurationMarshaller.java:326)
    at com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions(SecurityConfigurationMarshaller.java:246)
    Caused by: com.sap.engine.lib.xml.util.NestedException: Illegal conversion
    at com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63)
    at com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72)
    I am getting error in component controller doInit() method and below is the code
              XYZ model = new XYZ ();
                 Request_XYZ  request= new Request_XYZ(model);
                 Zxyz details = new Zxyz(model);
                                              details.setLanguagecode("");
                 details.setZuser("");
              details.setMessagenumber("");
                 request_Zxyz.setZxyz(details );             
                  wdContext.nodeRequest_XYZ().bind(request);
    If anyone know the reason of this error please help.
    Regards,
    Shweta

    HI GLM,
    If i comment the code in component controller i get the screen, but when i initialize the model and parameters in doInit() method i get error. I am using 5 web service and getting same error for all, so i have commneted rest and currently dealing with one.Below is the code,
                EventDetails model = new EventDetails();
                 Request_ZcpexGetEventDetails request_ZcpexGetEventDetails = new    
                                               Request_ZcpexGetEventDetails(model);
                 ZcpexGetEventDetails getEventDetails = new ZcpexGetEventDetails(model);
                 getEventDetails.setLanguagecode("");
                 getEventDetails.setZuser("");
              getEventDetails.setMessagenumber("");
                 request_ZcpexGetEventDetails.setZcpexGetEventDetails(getEventDetails);             
                              wdContext.nodeRequest_ZcpexGetEventDetails().bind(request_ZcpexGetEventDetails);
    Below is the exception trace
    Root Cause
    The initial exception that caused the request to fail, was:
       com.sap.engine.lib.xml.util.NestedException: Illegal conversion
        at com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63)
        at com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72)
        at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110)
        at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56)
        at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43)
    Detailed Exception Chain
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(name=com.dts.app.dtsapp.DTSapp, id=2370e7916c5711de8f22001e0b5c3568). The causing exception is nested. RID=236ffd306c5711de992e001e0b5c3568
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:638)
      at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:220)
      at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:232)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
      at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
      at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
      at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
      at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
      at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
      at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
      at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
      at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
      at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
      at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
      at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
      at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
      at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
      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:152)
      at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
    Caused
    by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException:
    Exception on creation of service metadata for WS metadata destination
    'DEFAULT_WS_EVENTDETAILS_METADATA_DEST' and WS interface
    'ZCPEX_GET_EVENT_DETAILS_WSD_PI'.
    One possible reason is that the metadata destination
    'DEFAULT_WS_EVENTDETAILS_METADATA_DEST' has not been properly configured; check
    configuration.<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1034)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)<BR>  at
    com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.&lt;init&gt;(WSTypedModel.java:41)<BR>  at
    com.dts.model.eventdetails.EventDetails.&lt;init&gt;(EventDetails.java:52)<BR>  at
    com.dts.comp.DTCComp.wdDoInit(DTCComp.java:184)<BR>  at
    com.dts.comp.wdp.InternalDTCComp.wdDoInit(InternalDTCComp.java:420)<BR>  at
    com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160)<BR>  at
    com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:230)<BR>  at
    com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:249)<BR>  at
    com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:209)<BR>  at
    com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:513)<BR>  at
    com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1234)<BR>  at
    com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:150)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)<BR>  at
    com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)<BR>  at
    com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)<BR>  at
    com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:75)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:568)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:588)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:250)<BR>  at
    com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:635)<BR>  ...
    41 more<BR>Caused by:
    com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException:
    GenericServiceFactory initialization problem. [Problem with WSDL file parsing.
    See nested message.]<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:303)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:234)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:202)<BR>  at
    com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:181)<BR>  at
    com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)<BR>  ...
    67 more<BR>Caused by:
    com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException:
    Problem with WSDL file parsing. See nested message.<BR>  at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:704);at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.generateAll(ProxyGeneratorNew.java:410);at
    com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.loadProxy(DGenericServiceImpl.java:130);at
    com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.&lt;init&gt;(DGenericServiceImpl.java:65
    ;at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:280)<BR>  ...
    71 more<BR>Caused by:
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationMarshallerException:
    com.sap.engine.lib.xml.util.NestedException:
    com.sap.engine.lib.xml.util.NestedException: Illegal
    conversion;at
    com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions_WSPOLICY_12_NS(SecurityConfigurationMarshaller.java:326)<BR>  at
    com.sap.engine.services.wssec.srt.features.configuration.SecurityConfigurationMarshaller.unmarshalAssertions(SecurityConfigurationMarshaller.java:246)<BR>  at
    com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.processAlternative(PolicyConvertor.java:195)
    com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.unmarshal(PolicyConvertor.java:92);
    at com.sap.engine.services.webservices.espbase.configuration.PolicyConvertor.unmarshalAlternatives(PolicyConvertor.java:135);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.createBindingData(ConfigurationBuilder.java:376);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.createBindingData(ConfigurationBuilder.java:356);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.create(ConfigurationBuilder.java:193);at
    com.sap.engine.services.webservices.espbase.configuration.ConfigurationBuilder.create(ConfigurationBuilder.java:158);at
    com.sap.engine.services.webservices.espbase.client.ProxyGeneratorNew.loadWSDLapi(ProxyGeneratorNew.java:699)
    84 more Caused by: com.sap.engine.lib.xml.util.NestedException:
    com.sap.engine.lib.xml.util.NestedException: Illegal conversion;at
    com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:377;at
    com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398;at
    com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240);...
    85 more Caused by: com.sap.engine.lib.xml.util.NestedException: Illegal
    conversion;at
    com.sap.engine.lib.xsl.xpath.xobjects.XObject.toXBoolean(XObject.java:63;at
    com.sap.engine.lib.xsl.xpath.xobjects.XBoolean.execute(XBoolean.java:72;at
    com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:110;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43;at
    com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51;at
    com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132;at
    com.sap.engine.lib.xsl.xslt.XSLTopVariable.process(XSLTopVariable.java:42;at
    com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:360;...
    Regards,
    Shweta

  • How To Consume UME services in Web Dynpro applications

    Dear Friends,
    I am developing a new web dynpro application in which i want to get the user related information in my dynpro code. I have used com.sap.secuirty.jar file in class path -> lib of my project.
    I have written code sth like this.
    IUser user = null;
    String username = user.getCurrentUser().getSAPUser();
    and defined sap.authentication as a application variable to fetch user creadentials from portal run time.(user logs in to the portal and dynpro application fetches user credentials from portal). When i do this, the login window appears twice and user needs to enter his credentials more than once. If I remove sap.authentication parameter from the application then i am not able to get the user credentials. Could you please tell me the right method of fetching the user credentials in web dynpro application? Do we need to use sap.authentication? do we need to include sharing reference of the usermanagement in our application?
    kindly share your knowledge.

    These might be good places for you to start.
    [User|http://help.sap.com/saphelp_nw04s/helpdata/en/80/45da9619d24b61bb869c31ef3b780a/frameset.htm]
    [Protecting Access to the Web Dynpro Application Using UME Permissions|http://help.sap.com/saphelp_nw04s/helpdata/en/f3/a64d401be96913e10000000a1550b0/frameset.htm]
    -Michael
    Edited by: Michael Shea on Sep 2, 2008 8:24 AM
    Edited by: Michael Shea on Sep 2, 2008 8:25 AM
    Fix link

  • The Web Dynpro application 'UWL' has expired

    Hi ALL,
    We are using Enterprise portal 7.0. and backend SRM server
    When the user login into portal it will take him to the UWL page
    in that the user click for any "Approve shopping cart" the error message showing
    " The web dynpro application *'UWL' has expired. restart the application. choose 'refresh' in the iview tray or use the*
    *browser 'refresh' button to restart the iview"*
    user not getting the error message every time. error coming occasionally
    we suggest the user to clear the cookies and restart the browser and relogin.
    but some times it works some times not
    Can any one know the exact problem (any parameters has to be change or any other solution)?
    Regards,
    Abdul Razzaq
    SAP NW.BASIS Consultant

    Dear Abdul ,
    Hope you are doing good.
    We have seen similar cases of  WD Session Expired error message when the  jsessionid cookie issued by the server with the initial requests was not returned from the client with subsequent requets to the server. The only way to ascertain whether this is the case in your system will be by checking the HTTP watch trace (note 1558903 - How To Trace a Portal Scenario Using HttpWatch).
    As the jsessionid cookie is used for session management, when it is missing from the request headers the correct session could not be retrieved and as result new session will be created for that user. Set the parameter JSESSIONID.CookieDomain to "NONE" as mentioned in the sap note: 791765 and see if the issue persists. This configuration should be accessible in
    Config Tool -> expand the tree "cluster-data" -> "Global Server Configuration" -> "services" -> "servlet_jsp" -> Go to "Global
    Properties". Do make the changes, save the customization and then restart the complete SAP server (not just the JAVA server nodes).
    Kindly go through the note completely.
    Also make sure that the SystemCookiesDataProtection and SystemCookieHTTPProtection is set in the HTTP Provider Service on
    the server nodes.
    Do make the changes,save the customization and then restart the complete SAP server.
    Thank you and have a nice day :).
    Kind Regards,
    Hemanth
    SAP AGS

Maybe you are looking for