Could not run Web dynpro application

Hi
I am having ECC 5.0, now I am trying to run Web Dynpro application which is already existing,I could not run this application. In SE84 that applications are available, but in SE80, not showing. Please suggest me what could be the reason.

guess u need ECC6 for Webdynpro.For more info plz chk this link:
Web Dynpro for ABAP
Edited by: Kalyan Chakravarthi on Jan 30, 2009 11:28 AM

Similar Messages

Can not run web dynpro application

Hi,
im new in developing with web dynpro in java.
I installed:
SAP NetWeaver 7.1 Composition Environment SP03 PAT0000 (Netweaver Developer Studio)
Build id: 200710302120
and
SAP NetWeaver 7.0 Java Trial Version (with the application server).
The WebAS is running and i configured it in the developer Studio in preferences SAP AS JAVA.
I already developed a little web dynpro application. I want to test this application now.
I choosed deploy. After this, i clicked on "Deploy new archive and Run" on the application (followed after the steps of a tutorial).
After that step i am getting an error (in a popupwindow), which says
"wrong parameter - http://dmhpnb34:-1/webdynpro/dispatcher/local/Welcome/WelcomeApp?SAPtestId=8" ?
Does anybody know what this error means ?!

Hello
I already developed a little web dynpro application
have you developed the application in another version or the same which you mentioned in your post
if you developed in any other version , try to create everything from scratch in the newer version and then try to deploy again
Regards
Chaitanya.A

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

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. at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1034) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248) at
com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41) at
com.dts.model.eventdetails.EventDetails.<init>(EventDetails.java:52) at
com.dts.comp.DTCComp.wdDoInit(DTCComp.java:184) at
com.dts.comp.wdp.InternalDTCComp.wdDoInit(InternalDTCComp.java:420) at
com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:160) at
com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:230) at
com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:249) at
com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:209) at
com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:513) at
com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1234) at
com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35) 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.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100) at
com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:75) at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:568) at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:588) at
com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:250) at
com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:635) ...
41 more Caused by:
com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException:
GenericServiceFactory initialization problem. [Problem with WSDL file parsing.
See nested message.] at
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:303) at
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:234) at
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:202) at
com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:181) at
com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429) ...
67 more Caused by:
com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException:
Problem with WSDL file parsing. See nested message. 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.<init>(DGenericServiceImpl.java:65
;at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService_NewInstance(GenericServiceFactory.java:280) ...
71 more 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) 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

I could not run any java application

I could not run any application program( even thouht the simplest one such as helloword). It would give NoClassDefoundError as:
Exception in thread "main" java.lang.NoClassDefFoundError: Welcome1
Press any key to continue . . .
I use text pad editor. First I compile it, there is no error. But when I try to run ( by click run java application program button ) it gives me the same error message.
I also always have compile error such as no class define when I try compile the program which need to import user defined class from differerent package. ( even though I did put all the classed in the same directory and also use import statement)
I did try to run many other applet programs which do not use any user defined class, in this case every thing work fine and I could run the program.
That mean I could run simple applet program but not application, also i always have compile error when ever I tried to import user defined class.
I'm afriad there is some thing wrong with the sdk and java enviroment, therefore I did try to uninstall the program and redownload from the web( I try both version 1.3 and 1.4 many time, and I did check the size of the application when I finish down load) but I still got the same problem.
My computer operating system is WinMe.
I appreciate any help

You probably have to set some settings for text pad. It looks like the java interpreter could not find your class, which most likely means that the classpath setting is not set properly.

Running Web Dynpro Applications in Different Browsers

Hi,
I runned an Web Dynpro Application in different browsers(Opera, Firefox and Internet Explorer). The problem is that in Firefox is running fine, but in Internet Explorer some controls are missing and in Opera I got an Error Page that say the following:
An error has occurred:
"Failed to process the request."
Please contact your system administrator.
This page was created by SAP NetWeaver. All rights reserved.
Web Dynpro client:
Nokia Series 80 Client
Web Dynpro client capabilities:
User agent: Opera/9.25 (Windows NT 6.0; U; en), client type: op6, client type profile: op6, ActiveX: disabled, Cookies: enabled, Frames: enabled, Java applets: disabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
Accessibility mode: false
Web Dynpro runtime:
Vendor: SAP, build ID: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:13:14[UTC], changelist=455669, host=pwdfm101), build date: Wed Nov 14 08:48:35 GMT-03:00 2007
Web Dynpro code generators of DC agile.com/pmg_bonefish~webdynpro:
SapDictionaryGenerationCore: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:42[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:00:50[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:23[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:15:27[UTC], changelist=455669, host=pwdfm101)
SapGenerationFrameworkCore: 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:44:42[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:26[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:54:53[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:45:30[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-11:15:04:37[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-11:14:57:50[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwddispwda: No information available!
Web Dynpro code generators of DC sap.com/cafUIptn~common:
SapDictionaryGenerationCore: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:06[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro: 7.0013.20070703112649.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:28:49[UTC], changelist=454024, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:35[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
SapWebDynproGenerationCTemplates: 7.0013.20070717142021.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:42:07[UTC], changelist=455669, host=pwdfm101)
SapGenerationFrameworkCore: 7.0013.20060719095755.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:13:54[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:11[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary: 7.0013.20060719095619.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:23:29[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon: 7.0013.20061002105432.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:14:42[UTC], changelist=419384, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCore: 7.0013.20061002110128.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:32:21[UTC], changelist=419396, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates: 7.0013.20061002105236.0000 (release=645_VAL_REL, buildtime=2007-08-07:13:26:13[UTC], changelist=419377, host=PWDFM101.wdf.sap.corp)
Web Dynpro code generators of DC sap.com/tcwdcorecomp: No information available!
J2EE Engine:
7.00 patchlevel 109044.44
Java VM:
Java HotSpot(TM) Server VM, version: 1.4.2_09-b05, vendor: Sun Microsystems Inc.
Operating system:
Windows 2003, version: 5.2, architecture: x86
I don´t know is the problem I have in both browsers Internet Explorer and Opera are from the browser or from the layout I´m using in Web Dynpro.
regards

Hi Aida,
For getting an information of the Web Browsers supported by SAP NetWeaver, check out the following link:
[http://service.sap.com/pam|http://service.sap.com/pam]
To access the Product Availability Matrix (PAM), you will need a sUser Login Name.
For Reference,
http://help.sap.com/saphelp_nw04s/helpdata/en/79/23c7410400c717e10000000a155106/frameset.htm
Regards,
Alka.

Run a web dynpro application encounter WDUMException exception...

Dear guys,
We currently encounter a error when we run a web dynpro application.
That is, once a user click a url which will redirect to the enterprise portal,
the com.sap.tc.webdynpro.services.sal.um.api.WDUMException is thrown.
I have checked the cause of the exception is that "if there is no user (neither authenticated nor anonymous user) attached to the current session"
The following is our situation:
When linking to EP domain(ex. http://sapep.xxx.com), single signed on wil automatically process.
The url which I mentioned above is something like "http://sapep.xxx.com/portal?doc=xxx&ver=2010"
Our web dynpro program will invoke the IWDClientUser api initially for get the currently logon user's information.
And this is caused the WDUMException.
We think that the error is because that the session is not created while loading the web dynpro application,
so that, the system can't get the cuurent user with a non-user session.
The situation is not often happened. We think this is because of the system service issue.
So we try to prevent this problem with the following mechanism:
When the excpetion is thrown, we invoke a waiting program to let the system has time to generate the require session.
So when invoke the IWDClientUser, this exception can be prevented.
Any suggestion.please advise, thanks.

Try using WDPortalUtils.isRunningInPortal() method to see if the session (somehow) disconnects
Hi,
We check the method you proposing, but seems it's not the method to check the session of the current user.
The API of WDPortalUtils.isRunningInPortal() is as follows:
public static boolean isRunningInPortal()
        Checks whether or not the Web Dynpro application is running the the portal environment or not.
        Returns:
              true if the Web Dynpro application is running in the portal environment, false otherwise.
Is there any other API which can check the current session alive or not?
thanks.

Exception not caught while executing web dynpro application

Hello all,
I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
Please suggest how to resolve the isse?
Regards,
anil

sorry...posted in wrong forum...

Web Dynpro application does not apply portal theme

Hi Guys,
We created a new portal theme and assigned it to our users. The portal desktop gets assigned succesfully and portal applications also show the new theme colors. But all web dynpro pages still show in the blue SAP theme. This issue only occurs on our development portal, when we import the same theme on our test portal is all works fine.
I also tried to assign the WebDynpro parameters "sap.useWebDynproStyleSheet" and "sap.theme.default" and then the web dynpro applications are indeed forced into the portal theme. However, that is no soluition since all web dynpro applications then use the theme including SAP applications like the NetWeaver Administrator.
We looked at OSS note '1446099 - Web Dynpro application not displayed
in customer theme' but the stylesheets are not different.
sap portal sytlesheet: UR=7.31.0.14.1
Web Dynpro Style sheet: UR Version=7.31.0.14.0
The portals in which the theme does work have the same stylesheet versions as mentioned above.
We also created an OSS message for this so if we solve it that way I will update this message. But if there is anyone on this forum that might have an idea that it would be highly appreciated. If the problem takes too long to solve we will perform a refresh from a portal that works but I hope that we will be able to find the reason of this behavior.
Kind Regards,
Nico van der Linden...

In theory, these versions should work correctly.
You can compare the patch levels applied on your dev portal and test portal - specifically compare the version/patch for the component EPPSERV*.SCA - and see if you have any differences there.
Thanks,
Shanti

How to get User Id in Web dynpro application

Hi Experts,
I am running web dynpro application with authentication checkbox set. I want to display user id of the user in my application. I am using following code in Init method of component controller.
IWDClientUser wdUser = WDClientUser.getCurrentUser();
WdContext.currentContextElement().setUserName           (wdUser.getClientUserID());
Here I am getting some integer value as userId.
I am not using Portals, so solutions suggested for portal are not useful for me .
Is there any way to get this uset id.
Thanks in advance

hi
try this piece of code
          IWDClientUser wdUser = WDClientUser.getCurrentUser();
          IUser user = wdUser.getSAPUser();
          if (user != null)
                    IUserAccount[] acct = user.getUserAccounts();
                    if(acct[0] != null)
                              String strUserid = acct[0].getLogonUid();
wdContext.currentZtms_Fm_Regupdate_InputElement().setAssoid(new String(strUserid));
Note: Defining the IUser will show an error. To resolve this, within the properties of
the project, choose Java build path -> Libraries -> Add external jars ->
com.sap.securities -> lib -> com.sap.security.api. Open this file and retype the code.

Uncaught exception while executing web dynpro application

Hello all,
I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
Please suggest how to resolve the isse?
Regards,
anil

Hi Anil,
I'm also getting the same run time error. When I try to activate the Web Dynpro component, I'm getting error that the component is locked by the user.
Please let me know how you solved this issue.
Thanks in advance for the quick response.
Thanks & Regards,
Jay

Uncaught exception when executing web dynpro application

Hello all,
I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
Please suggest how to resolve the isse?
Regards,
anil

Dear Anil,
What type of WD is it ?
Do you get the error when you trigger some sort of event ?
Is it when first launch the WD ?
Can you be more specific and share with us the code where this is dumping ?
You can also check this link
[CX_WDR_RT_EXCEPTION' - How to catch it?;
Kind Regards
/Ricardo Quintas

How to make use of Portal service in the web dynpro application

hi
I have some portal service and how to use that in the web dynpro application.
and also what is the main diff between Portal Component and web dynpro application.
do we required portal to run web dynpro application.
thanks
mmukesh

Hi,
>> I have some portal service and how to use that in the web dynpro application.
Yes. U can use Portal service in webdynpro. Check the link given by subathra.
>> and also what is the main diff between Portal Component and web dynpro application
Portal Components are components designed to run in portal server while webdynpro application can run in J2EE WebAS.
>> do we required portal to run web dynpro application.
No for general cases. Just WebAS is sufficient to run webdynpro appl. But if u use portal service in ur webdynpro appl, then make sure both (portal service and webdynpro appl) run on same J2EE engine. That is mandatory.
Regards,
Vijai

Running ABAP Web Dynpro Application without host entry of web server

Hi All,
I am trying to run a web dynpro application, its working fine when I have done host entry (host nam.domain.extension) of web server.
But when I remove this entry from host file it not runs.
Can you tell me the posibility of running this application without host entry? Based on this possibility I have to proceed my work. Please guide me.
Thanks and Regards
Sudhir Gupta

Hi Sudhir ,
See the below link , its necessary to provide FQDN.
http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm
Regards
Yash

Not Gettng Web dynpro abap application creation menu in SE80

Hi all,
I m new in WDA.I wanted to create one web dynpro application in abap with se80. however, in se80 i m not getting any option to create the application .
IF i go to other objects in the main menu ie. (prgrams-->other objects) from se80 , i get the option for web dynpro application.
If someone knows please tell me How to add this utility in list box in the repository browser?
Regards,
Jigs

>Please can you tell me what are the h/w requirements to use web dynpro with ABAP
What exactly are you looking for?
You can check the Platform Availability Matrix (PAM) on the Service Marketplace (http://service.sap.com/pam) to see the supported environments of 04S. However Hardware Requirements (sizing) is not cut and dry as it depends upon which business applications your are running and how many users you must support.
As far as client requirements, ABAP development is all done on the central server. All the client developer needs is the SAPGui.
If you want to try out Netweaver04S ABAP, a free evaluation copy of the server installation can be downloaded from SDN. The hardware requirements for running this evaluation version are listed on the download page.

Could not run Web dynpro application

Similar Messages

Maybe you are looking for