About test a web dynpro application

Hi, experts
When i test a web dynpro application, the IE
web page constantly refresh.
Who encounter this issue?
This is a very strange problem.

which IE are you running?
Internet Explorer 5.5 or higher or Firefox 1.0 or higher, will work
Mine is Internet Explorer 6.0, sp2 working fine.
No Support for '_' in Host Names
The browser does not accept cookies if a host name contains the underscore character '_'.
Since Microsoft Internet Explorer 6.0 and MS Internet Explorer 5.5 including security patch MS01-055 cannot accept any domain names with underscore characters, session cookies cannot be saved. This will result in terminations when navigating within a Web application.
http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm
Abhi

Similar Messages

Web Dynpro applications not working on ECC 6.0 IDES

Hi,
I'm new to Web Dynpro and developed a custom Web Dynpro (including the application) on a ECC 6.0 IDES system. It's simple with a couple of input fields. When I test it (either via SAP GUI 7.1 or 7.2, or Web GUI), it appears on the browser ok but the screen is frozen. I can't enter anything into the fields, etc. I also tested SAP Web Dynpro applications and they act the same way, frozen screen. There aren't any errors displayed or any runtime errors in ST22. Please advise. I searched this forum but didn't see any issue similar to mine. The IDES vendor suggested I post the issue on SDN.
John

I guess it has do to with some sort of browser's font size or view settings.
press ctrl +0 make the zoom 100% and font size medium and try again.
thanks
sarbjeet singh

Error - Creating a Web Dynpro Application Accessing ABAP Functions

Dear All,
we are trying to implement a web dynpro application with accessing ABAP functions.
Previous tasks:
- insert the ABAP system into the SLD from the NWDI System (Transaction RZ70; the ABAP system is correctly insert into the SLD => technical systems)
- equipped the JCO connections with the web dynpro content manager (ping and test = OK)
Its the standard tutorial out of the SDN called Creating a Web Dynpro Application Accessing ABAP Functions.
Some hints:
- There are no errors after the implementation and the rebuild of the project in the NWDS
- The auto deployment works fine to the development runtime system. The application is shown in the Web Dynpro content manager
- The In the build log I found these entries:
System.err] [Invoked from com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:585)]
[System.err] java.net.UnknownHostException: FRASAPP562: FRASAPP562
[System.err] at java.net.InetAddress.getLocalHost(InetAddress.java:1191)
[System.err] at com.sap.s2x.tools.GUID.getnodeaddress(GUID.java:575)
[System.err] at com.sap.s2x.tools.GUID.<clinit>(GUID.java:179)
[System.err] at com.sap.s2x.tools.S2XGUID.getGUID(S2XGUID.java:19)
[System.err] at com.sap.ide.metamodel.core.i18n.LanguageState.createS2XID(LanguageState.java:191)
[System.err] at com.sap.ide.metamodel.core.i18n.S2XLanguageUnmarshaller.unmarshal(S2XLanguageUnmarshaller.java:52)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.loadLanguageState(TextPoolProxy.java:703)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.prepareLanguageForRead(TextPoolProxy.java:646)
[System.err] at com.sap.ide.metamodel.core.i18n.TextPoolProxy.isEmpty(TextPoolProxy.java:222)
[System.err] at com.sap.ide.webdynpro.checklayer.MDOChecker.check(MDOChecker.java:23)
[System.err] at com.sap.ide.webdynpro.checklayer.view.ViewChecker.check(ViewChecker.java:52)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ViewControllerChecker.check(ViewControllerChecker.java:96)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:119)
[System.err] at com.sap.ide.webdynpro.checklayer.controller.ControllerChecker.check(ControllerChecker.java:56)
[System.err] at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:181)
[System.err] at com.sap.ide.webdynpro.checklayer.component.ComponentChecker.check(ComponentChecker.java:56)
[System.err] at com.sap.ide.webdynpro.generation.Generation.check(Generation.java:2039)
[System.err] at com.sap.ide.webdynpro.generation.Generation.generatePersistentComponent(Generation.java:1296)
[System.err] at com.sap.ide.webdynpro.generation.console.GenerationConsole.generate(GenerationConsole.java:175)
[System.err] at com.sap.webdynpro.generation.ant.GenerationAnt.main(GenerationAnt.java:50)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err] at java.lang.reflect.Method.invoke(Method.java:324)
[System.err] at com.sap.webdynpro.generation.ant.WDGenAntTask.execute(WDGenAntTask.java:219)
[System.err] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[System.err] at org.apache.tools.ant.Task.perform(Task.java:364)
[System.err] at org.apache.tools.ant.Target.execute(Target.java:341)
[System.err] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[System.err] at org.apache.tools.ant.Project.executeTarget(Project.java:1214)
[System.err] at com.sap.tc.buildplugin.techdev.ant.util.AntRunner.run(AntRunner.java:112)
[System.err] at com.sap.tc.buildplugin.DefaultAntBuildAction.execute(DefaultAntBuildAction.java:61)
[System.err] at com.sap.tc.buildplugin.DefaultPlugin.handleBuildStepSequence(DefaultPlugin.java:213)
[System.err] at com.sap.tc.buildplugin.DefaultPlugin.performBuild(DefaultPlugin.java:190)
[System.err] at com.sap.tc.buildplugin.DefaultPluginV3Delegate$BuildRequestHandler.handle(DefaultPluginV3Delegate.java:66)
[System.err] at com.sap.tc.buildplugin.DefaultPluginV3Delegate.requestV3(DefaultPluginV3Delegate.java:48)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[System.err] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[System.err] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[System.err] at java.lang.reflect.Method.invoke(Method.java:324)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.maybeInvoke(PluginHandler2.java:350)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.request(PluginHandler2.java:102)
[System.err] at com.sap.tc.buildtool.v2.impl.PluginHandler2.build(PluginHandler2.java:76)
[System.err] at com.sap.tc.buildtool.PluginHandler2Wrapper.execute(PluginHandler2Wrapper.java:58)
[System.err] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1723)
[System.err] at com.sap.tc.devconf.impl.DCProxy.make(DCProxy.java:1495)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.build(CBSBuildController.java:727)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.execCommand(CBSBuildController.java:503)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.evalCmdLine(CBSBuildController.java:442)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.run(CBSBuildController.java:314)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.exec(CBSBuildController.java:252)
[System.err] at com.sap.tc.buildcontroller.CBSBuildController.mainLoop(CBSBuildController.java:207)
- Im able to start the application out of the Web Dynpro content manager with run => only the user interface is displayed without any functionality
- The normal start over the NWDS fails => error text
com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/J08_Flugdat_Daventdcflight~xxx.com' and application 'FlightListApp' are not deployed on the server. Please check the used URL for typos.
There two different URLs in use.
Start via NWDS:
http://frasapp562:50000/webdynpro/dispatcher/J08_Flugdat_Daventdcflight~xxx.com/FlightListApp
Start via web dynpro content manager:
http://frasapp562:50000/webdynpro/dispatcher/xxx.com/aventdc~flight/FlightListApp
For test purposes, we started the BAPI (BAPI_Flight_Getlist) on the ABAP system directly. It works.
Any ideas about the system behaviours (different URLs and missing functionality)?
Thanks a lot in advanced!
Best regards
Christoph

The Error has been solved The implementation of a method was missing....
Thx
Christoph

Web Dynpro application needs to never expire.

Hi
I have a Web Dynpro application (NW2004 SP12) that displays spreadsheet like sales data to anyone who walks past the screen in a common area in the office/s. It should therefore run unattended. It refreshes the data on a timer. The data comes from a back-end aRFC. Everything works fine but about every 1.5 days the application times out (session expires) and needs to be re-opened (this seems to be a large administrative problem to re-login at all the deployment sites).
It gives an error 500application has expired. Please restart with the refresh button
In testing/troubleshooting I used the direct URL to the application running on WAS and not through a Portal iView.
I also changed the System destination from using SSO to using a dedicated user to the back-end.
Does anyone have an idea on how to auto refresh a Web Dynpro application or auto-renew the session so that it can run forever or a way to re-login automatically?
Thanks in advance,
Rick Viljoen

Hi Isidro
Yes, this was my final solution. Here is the code for the htm page. It will refresh/reload every 6 hours. Hope it helps.
Regards,
Rickus
<html>
<head></head>
<body>
<div id = div1></div>
<script type="text/javascript">
function putIF(hldr,x,y,w,h,url) {
 // Iframe
 holder=document.getElementById(hldr);
 holder.style.position ='absolute';
 holder.style.left=x;
 holder.style.top=y;
 holder.style.width=w;
 IF=document.createElement("iframe");
 IF.setAttribute("height", h);
 IF.setAttribute("width", w);
 IF.setAttribute("src", url);
 if (holder.hasChildNodes()) {
 var oChild=holder.children(0);
 holder.removeChild(oChild);
 holder.appendChild(IF);
 var myDate=new Date();
 window.status="Last reload on: " + myDate;
function refreshiframe() {
 myWidth = document.body.offsetWidth-21;
 myHeight = document.body.offsetHeight-4;
 putIF("div1","0px","0px",myWidth,myHeight,"http://<server>:<port>/webdynpro/dispatcher/local/SalesD/SalesD?j_user=xxx&j_password=ppp");
 window.setTimeout(refreshiframe, 21600000);
refreshiframe();
</script>
</body></html>

Mass upload through Web Dynpro application possible?

We want to develop a custom aplication with Web Dynpro ABAP for master data maintenance. About 90 % will be done manually but we also want to have the possibility to do mass uploads (comparable with LSMW's in SAP R3 for win gui transactions: users send us a spreadsheet and we load it for them using a LSMW). I found one option by building Adobe Interactive form offline scenario using xml messages but I don't want to be forced to use Adobe only to enable mass uploads that will only happen in 10 % of the cases.
I am loking forward to your suggestions!
kind regards
Angelique Heutinck

I got a very useful answer from Thomas Jung (SAP) via a site he did setup with a couple of other SAP experts, also see http://enterprisegeeks.com/blog/2009/03/31/abap-freak-show-april-1st-acf-updownload-in-web-dynpro-abap/comment-page-1/
My question:
I think this new UI element ACFUpDownload cannot be used to do mass uploads/updates of data that need to be stored in SAP tables?
Answer Thomas:
This UI element is just about the transfer of data from the client machine to the server. It has nothing to do with how the data is used or processed after upload. Think of it as the equal to the CL_GUI_FRONTEND_SERVICES class and methods GUI_UPLOAD and GUI_DOWNLOAD.
My question:
Is there a tool like LSMW, CATT, eCATT that we can use for recording webenabled transactions (applications developed in Web Dynpro ABAP)?
Answer Thomas:
You shouldnu2019t need a tool like LSMW, CATT, eCATT that is tied to the user interface. With WDA you should be using MVC to design your application. This is part of the reason for MVC so that you have a clear separation of the model - business logic. You should always have a reusable class that can be called to input and create data with the same validations without going through the user interface. This is the process that SAP is following as we create new WDA screens. We use the enterprise services and their implementation classes as the Model for the WD Components. This ensures that you always have a clear API to use to mass import data.
Although we wouldnu2019t recommend doing any kind of mass data load via the user interface any longer - eCATT will be supported for automated testing of Web Dynpro ABAP applications as of NetWeaver 7.0 Enhancement Package 2.

Passing a parameter while calling a web dynpro application on portal

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

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

Error while implementing a web service in web dynpro application

HI All,
I am trying to use a webservice in a web dynpro application.
Web service description:- This is a very simple application which takes two String inputs and when submitted displays the string in the concatenated form.
Web dynpro:- I used this web service in the web dynpro as an adaptive web service model.
The Layout design consists of two input fields which are mapped to the request fields
ex : - Request_Add.Add.S1 and Request_Add.Add.S2
A text area to display the response:- Request_Add.Response.AddResponse.Response
And a button which invokes the execute method
public void onActionWebserviceCall(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
 //@@begin onActionWebserviceCall(ServerEvent)
 wdThis.wdGetWebserviceCompController().executeRequest_Add();
 //@@end
When I am trying to run the application I am getting error:-
Exception on execution of web service with WSDL URL 'http://<Host>:<Port>/EjbWebservice/Config1?wsdl' with operation 'add' in interface 'EjbWebserviceVi_Document'
Kindly reply.
Thanks
Neha

Hi,
Yes I have tested the web service in Navigator . The WSDL is also properly generated.
I have not publish the web service in UDDI but as per my understanding this is not necessary. please correct me if I am wrong.
Thanks
Neha

Application specific theme in CE7.1 web dynpro application

Hi,
where can I find documentation about setting up application specific themes for Java Web Dynpro applications running in Composition Environment 7.1? I've found documents that refer to the Visual Administrator but since it doesn't exist anymore in CE7.1 there must be a different way.
Regards,

Hi Kevin,
Yes, charts are going to be supported in WD html in next versions of VC( Q3 2008).
Regards,
Kobi.

Delete a file from the KM in a Web Dynpro application

Hello,
We need to delete a file from the KM in a Web Dynpro application.
We have a file name (filename.txt) and its path (/documents/Test/), how can we completely delete the file from the KM?
Thanks,
Gil

Hi venkata reddy,
You wrongly mentioned system admin instead of content admin
Go to Content administration not in the system administration
if u delete the file manually in the portal you can go with
go to Content administration -> KM Content -> go to Particular document -> just tick the check box which doc u want delete -> go to selection -> u will find delete .
Regards,
P.Manivannan

Problem with starting the Web Dynpro Application

Hello,
I have a problem with my web dynpro application, which is in our SAP Portal. We have three different systems (development, test, production). In production always the follewing error message occurs:
The URL https://zsil2401.servers.wacker.corp:9004/sap/bc/webdynpro/sap/ZPLM_EN_FORM_300MM/ was not called due to an error.
Note
The following error text was processed in the system P1A : is not a valid attribute type.
The error occurred on the application server zsil2401_P1A_04 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: GETATTRIBUTE_RTTI of program CL_WDR_CONTEXT_NODE_INFO======CP
Method: INIT_ATTRIBUTES of program CL_WDR_CONTEXT_NODE_INFO======CP
Method: CREATE_FROM_STRUCT of program CL_WDR_CONTEXT_NODE_INFO======CP
Method: IFWDR_RG_CTRL_HANDLE~INIT_CONTEXT of program SAPLWDR_RG_GENERATED_SRC_API
Method: IFWDR_INTERNAL_API~INIT_CONTEXT of program SAPLWDR_RG_PROXY_FACTORY
Method: CONSTRUCTOR of program /1BCWDY/35DSOWFU6YQV6I81U8VG==CP
Method: IF_WDR_CLASSLOADER~GET_COMPONENT_CONTROLLER of program /1BCWDY/35DSOWFU6YQV6I81U8VG==CP
Method: CONSTRUCTOR of program CL_WDR_DELEGATING_COMPONENT===CP
Method: CONSTRUCTOR of program CL_WDR_CLIENT_COMPONENT=======CP
Method: CONSTRUCTOR of program CL_WDR_CLIENT_APPLICATION=====CP
Some User get this message also in test an development. What could be the reason?
Note: Nothing has changed in coding or context.....this error occurs without any changements
Thanks for your help
Best Regards
Martin

Hi,
May be you can put an external breakpoint in the method "_get_attribute_rtti"(of class CL_WDR_CONTEXT_NODE_INFO).
From that you can find out which attribute is causing the dump , and try to solve the issue . May be some data dictionary object is not transported to production.(Assuming that you have permission to put breakpoints in production system..:))
Aditya.

I want to editable description field in my web dynpro application

Hi expert,
The requirement is to make the Description field editable. However, the container for the dynpro only appears to allow for a certain type of action and is essentially used to display the Line Item details, giving no option to change the Line Item Description.
so i want to editable in this description field in my web dynpro application /SAPSRM/WDC_DOTC_PC_I_BD .
Kindly give me soulation ASAP.
Thanks and Regard's.
Vikash

Thanks for the reply.
The name of the view is V_PC_DOTC_ITM on which we have the records. On each line item there is a description field which is of type (LinkToAction). I want to enable user so that it can change the Description text (I will handle the action). Also, if you have any idea about updating the database table from here as it needs to be updated in BBP_PCPOS table.
-vikash

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

The Web Dynpro application 'PageBuilder' has expired

Hi Alll,
We are implementing ESS/MSS and the Portal was working fine.
We set it up for SSL/https and it was working just fine. However when we call it from reverse proxy server the web dynro applications through the following error:
The Web Dynpro application 'PageBuilder' has expired. Restart the application. Choose 'Refresh' in the iView tray or use the browser 'Refresh' button to restart the iView
Details: No details available
When I tested this with a transaction iview they work just. Also when tested directly from Portal they work fine.
Can anyone assist on this please?
Thanks,
Mike

Hello Mike,
After a user is logged in and requested an ESS/MSS application. The pagebuilder service is requested to built the page.
When the user is still logged in but is not working with this application the pagebuilder receives a timeout after a while and the session is expired. The pagebuilder has sometimes the status stopped, you can see this in the Netweaver Administrator. (Search for the pb in the application area)
If an other user is requesting an application the pb service is started again and the page built again.
If you want to get rid of the warning you could set the "timeout" parameter to a higher value in the configtool.
Kind regards,
Marcel

How to display the error message during the web dynpro application runtime

hi,
 I'm a java developer,During i 'deploy and run ' a web dynpro application on server-1,if the application have some runtime errors. there are displayed many infomation about the runtime error,such as exception track,etc.
 But when i do the same on server-2,there just show something like:
 500 Internal Server Error
 SAP NetWeaver Application Server 7.00/Java AS 7.00
 Failed to process request. Please contact your system administrator.
but the server-1 will stop the j2ee engine.
how can do i make server-2 show detail error message as server-1. when i debug web dynpro application need these infomation.
Appreciate your inputs...
(Note:server-1 and server-2 have same software version)
Edited by: BingLin Zhong on Feb 18, 2008 2:13 AM

The Sap-Notes 962319:
1. Check in the Visual Administrator, "Licensing Adapter" -> "General" -> "SystemType" !
If it is set to "DEVELOPMENT_MODE", verbose error messages are shown.
If it is undefined, proceed with the next step.
If it is set to something else, only exception IDs are shown. In this case the only chance is to search for this exception ID in the default traces.
2. If the system type is undefined, then in the Config Tool "Configurations" -> "webdynpro" -> "sap.com" -> "tcwddispwda" -> "Propertysheet default" -> "DevelopmentMode" is evaluated. If it is "true", verbose error messages are shown.
3. If verbose error messages are required but still the short version is shown, you probably face an error message that is not raised by Web Dynpro but by other components of the NetWeaver. In the Visual Administrator set "Properties" -> "HTTP Provider" -> "DetailedErrorResponse" to "true".
4. In addition to the error page shown in the browser or client, important messages - including error messages and stack traces - are written to the log and trace files, e.g. to the default traces usr\sap\<SID>\<instance>\j2ee\cluster\server<number>\log\defaulttrace.trc.<number>.
a) In some cases, when an exception ID is included in the error message, the detailed error message can easily be retrieved in the log file.
b) When no exception ID is given, you have to search for the detailed error message in the log specifying time stamp and/or user ID.
Always consider restarting the system after making changes on the settings.
It is not recommended to switch the "SystemType" to an inappropriate value just for viewing verbose error messages. The system type potentially affects framework, applications and licensing in an perhaps unintended way.
In the past there was no distinction between different system types regarding error messages. For security reasons this distiction has been introduced. It is not intended to show stack traces in non-development systems in the future. SAP does not provide workarounds or patches to enable such a behaviour again.

The Web Dynpro Application 'Appl' has expired.

Hallo altogether,
i am a newbie in this area.
I maked a simple Web Dynpro with two views,
only for navigation test
and without data transport.
Everybody view consist of two elements:
one TXV_Field and one BTN_Element.
V_ONE:
TXV_ONE with a text "View one",
BTN_GO + action GO,
OP_TO_TWO,
IP_FROM_TWO
V_TWO:
TXV_TWO with a text "View two",
BTN_BACK + action BACK,
OP_TO_ONE
IP_FROM_ONE.
There are two links between views builds.
I cann my application APPL deploy without problem and without error messages.
I see my V_ONE im browser.
If i click the button BTN_GO ==>
The Web Dynpro Application 'Appl' has expired.
I controlled the file default.properties
the timeout = 3600.
what cann i do????
Thank,
vmath.

1. check ur server configuration windw> preference->j2ee-engine.
I have DeveloperStudio local on my PC.
There are following settings for j2ee-engine:
SAP J2EE-engine is installed on local host
System name: J2E
J2EE Instance: 0
SCS Instance: 1
BEN_1\sapmnt\J2E\SYS\profile\J2E_JC00_ben_1
BEN_1\sapmnt\J2E\SYS\profile\J2E_SCS01_ben_1
vmath

About test a web dynpro application

Similar Messages

Maybe you are looking for