Can I run WEB Dynpro in ECC 5.0 ?
Can I run WEB Dynpro in ECC 5.0 ?
Hi Namrata,
Read this thread,
Re: Can we work ABAP Webdynpro in ECC 5.0
Regards
Juan
Please reward with points if helpful
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 -
Abap 703 trial - can't configure web dynpro to work - reverting back to 702
Hi there
whatever I do I can't get Web dynpro to work in ABAP 703 trial -- WDY compiles etc - but always get IE explorer cannot find page when I try and run the WDY, -- I've activated all the SICF services and done the profile changes (RZ10) but still no good.
I've gone back to Abap 702 version which DOES work (even on W8 X-64)
The main reason for downloading this was to test and play around with Web Dynpro -- I'm past basic ABAP and OO stage !!!
If anybody has got Web dynpro in the 703 trial working PLEASE POST what you did.
Also there doesn't seem to be any software for manipulating the database (or adding volumes) like there was in the 702 release (DBM76.EXE). The documentation says use DB studio -- but WHAT do you do --there's no connect to the SAP DB.
I'm afraid even by SAP's OWN standards of documentation ||(usually if it exists is very obtuse) this trial version must take the record for "Helpful and relevant documentation:".
If you want to experiment with Web dynpro the documentation on how to set it up is fine for the 702 release so I suggest you stick to that until someon has worked it out for 7.03
CheersHi Alexander,
Thanks for sharing the solution , I did all the steps mentioned in the link http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30129979-011c-2e10-fb9b-a60e0d704c1d?QuickLink=index&…
The option mentioned by you was the only additional thing missing
Trial version : ABAP 703 64 bit. -
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 -
Can I use web Dynpro to access other database
Hi Experts,
Can I use web Dynpro to access other database? Like we have a Siebel Database, can web dynpro application read data from there? If yes, How can I do it?
Thanks a lot!!!
MHHi,
I think you should be able to write Native SQL in the supply function or the methods of the Assistance Class.
Hope this helps.
Regards,
Kedar -
How can we creat web-dynpro in SAP 4.6c?
Hi Gurus,
I'm new to the Web-dynpro technology, please help me in creating a simple web-dynpro.
My questions are:
1. can we create web-dynpro in SAP version 4.6c?
2. If yes then how?Hi Manjesh,
You cannt develop Web Dynpro's in 4.6C version. Web Dynpro's are introduced from ECC6.0 onwords.
Check this document about Web Dynpro for ABAP
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/77/3545415ea6f523e10000000a155106/content.htm
Edited by: suman kumar chinnam on Oct 17, 2008 12:51 PM -
Possible to run web dynpro apps without a portal??
Hi
Is it possible to run Web dynpro apps on a WAS without a portal?
ThxAh,
Absolutely possible.
Use url like
http://host:port/webdynpro/dispatcher/com.your-company/yourappdc/AppName
in your browser address bar
Valery Silaev
SaM Solutions
http://www.sam-solutions.net -
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,
ShwetaHI 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.<init>(WSTypedModel.java:41)<BR> at
com.dts.model.eventdetails.EventDetails.<init>(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.<init>(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 run web dynpro java application
I am new to Web dynpro java.
I have created sample application through NWDS. I wanna run the application in server.
please tell me from where I have to download the server and the steps to install the server.
I have installed sap management console, but frankly speaking don know how to proceed my next step.
Struggling for last two days and I believe my search will come to an end.
Thanks in advance.
P.S: If I post in the wrong column, admin please redirect me to the right place.Hi Ram,
I tried to download the Software according to your instructions. I could follow the path Installations and Upgrades -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER, but then the only choices left are:
SAP NETWEAVER 04
SAP NETWEAVER 7.0
SAP EHP1 FOR SAP NETWEAVER 7.0
SAP NETWEAVER CE 7.1
SAP NETWEAVER MOBILE 7.1
SAP NETWEAVER PI 7.1
Please look this [Install & Configure SAP NetWeaver Composition Environment 7.1 ehp1 (Preview Version)|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b057d7e3-b89e-2b10-1e9e-c426e967f8e1]
and [SAP NetWeaver Composition Environment 7.1|SAP NetWeaver Composition Environment 7.1]
Hope help full!!!
Regards
Vijay
Edited by: VijaySAPEP on Aug 11, 2011 11:50 PM
Edited by: VijaySAPEP on Aug 11, 2011 11:54 PM -
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.
regardsHi 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. -
Can I use Web Dynpros in SAP GUI
Hi,
I am a little confused about Web Dynpros for ABAP. Testing them the contents will always be presented in a browser using the defined URL.
However is it possible to run a Web Dynpro and using SAP GUI as presentation device. in another words is it possible to use them as traditional Dynpros were used.
Thanks in advance
TorstenHi Torsten.
You could just create a favourite in the main menu of SAP GUI.
Ther you just choose 'Other' and you should be able to select webdynpro application.
Here you have the choice whether the app should be started in a new browser windo or in the SAP GUI (which is basically also the browser).
Cheers,
Sascha -
Can I use Web Dynpro to provide Web Services
I know I can use Adative web services model to consume existing web services. But I have not seen any example to use Web Dynpro as the web service provider. Can this be done? If yes, how?
Thanks.Hi,
WebDynPro Java/ABAP are primarily User Interface technologies. Webservices are faceless (without UI ) components that provide certain functionality. Using UI technologies like WebDynPro Java/ABAP etc, we can build a face( UI ) to the webservices.
DnyPro itself means a screen & WebDynPro is for building web based applciations.
Hope this resolves your question.
Well, if you still want to use it as provider & if you have an existing web-service, the way to do it is, Right click on your WebDynPro ABAP component & select CREATE->Service Call. Build a Custom Controller or use the Component Controller to get the service using service type = Webservice proxy for your webservice. You can use this Component as a Used component in any other webdynpro components & use this to access webservices.
Thanks,
Phani
Edited by: Phani Rajesh Mullapudi on Oct 8, 2009 10:41 PM -
Can't navigate Web Dynpro iViews in SAP Portal Environment
We are facing a strange problem. When we try to Navigate other Tabs after refreshing Web Dynpro iView in Sap Portal Enviroment from Tray or Mouse right click or by external Popu window we are getting "can't execute code from a freed script" Error. Currently we have EP6 SP16.
Any help ?
Thanks
Satyam
Message was edited by: Satyanarayana MandapatiHi Sathya,
We have a similar Javascript error 'can't execute code from a freed script'.
How did you solved this problem.
Regards,
Sekar -
Strange JCO error when running Web Dynpro App
I am developing a new WebDynpro application to be deployed on our SAP
Portal interfacing with a SAP R/3 backend. The application uses
multiple JCo destinations (two for each model) all of which were
configured according the SAP guides (userid/password for metadata and
ticket for model data). The tests work fine for all connections.
However, we get HTTP 500 errors when executing the application. The
main message is : "com.sap.mw.jco.JCO$Exception: (101)
RFC_ERROR_PROGRAM: 'password' missing".
I have not been able to find anything to help and SAP themselves have yet to provide us an explanation.
- I was able to run the application fine in dev and it worked with this error occasionally appeared but now it always appears.
- Our portal is 2004s SP 10
- All of the JCOs are configured properly as per SAP instructions
- modeldata use SSO with user configured in R/3
- metadata use userid/password
- Another prototype Web Dynpro application has the same error.
- All of the Web Dynpro models are Adaptave RFC.
Any ideas would be greatly appreciated.Here is the full exception I am getting.
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.pwc.servicecenter.sapwai.wdmodel.types.Klassenart could not be loaded: com.sap.dictionary.runtime.DdException: failed to create provider: 'password' missing
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:932)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:176)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)
at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
at com.pwc.servicecenter.sapwai.wdcomponents.Z_CLASS_COPY_MAIN.wdDoInit(Z_CLASS_COPY_MAIN.java:97)
at com.pwc.servicecenter.sapwai.wdcomponents.wdp.InternalZ_CLASS_COPY_MAIN.wdDoInit(InternalZ_CLASS_COPY_MAIN.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1248)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:190)
at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
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:160)
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.dictionary.runtime.DdException: failed to create provider: 'password' missing
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:254)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:146)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:97)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:79)
at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
... 63 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:229)
... 70 more
Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'password' missing
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:457)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1015)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3238)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:91)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:123)
... 75 more
Maybe you are looking for
-
Hi guys, I have run out of space on a 320gig external HD so I have bought a new 650 Gig one. I am trying to restore from the back up to the new HD and keep getting the error "cannot copy xxxxxxx to the destination because its name is the same as the
-
Under which license type are InDesign Script provided ?
Hi guys, At work we use ID CS3. It comes with a script called "CropMarks". It's a great script but it doesn't really fit ours needs. I modifyed it (add bleed management & doesn't draw marks inside the selection) to fit ours wishes. Some other people
-
Timeout error when trying to create repository
Hello, I'm instaling ovm 3.2.3 and when I try to crete the storage repository from ovm manager I get a timeout error and it stops the creation. I've tried several times, I've reinstalled ovm and manager, but the error is always the same. I've look in
-
Trouble downloading (HOW TO UPDATE THE INSPIRATION BROWSER)
I have Photoshop Elements 10. Iwent into Start Menu, selected Control Panel (as directed) In the Programs category: I selected uninstall a program. I selected Adobe Photoshop.com - Inspiration Browser & uninstalled. I clicked the button to downl
-
Hi, I am developing an applet which uses Java Comm API. I'm running into some deployment issue. My understanding is that Java Comm API needs to have win32com.dll and javax.comm.properties files installed on the client machine for my applet to use Com