Web Dynpro application - HTTP or HTTPs

Hi all,
when is a web dynpro application called over http and when over https.
I have a web dynpro application (SICF - Logon Standard - not SSL) but the application is sometimes triggered with HTTPS.
How can i find this out?
regards

So If SSL is configured and installend on your System,
you can call your wd-application through HTTPS (beside HTTP) as well.
But if you enable SSL in SICF on the Logon,
only HTTPS will work, HTTP will not work anymore.

Similar Messages

Web Dynpro Application - HTTP 403 - Forbidden

Hi All,
We have created one application in Dev. environment. And it is working fine here.
But when we transport it to the QA system, we are getting 403 forbidden error.
What has happened?
URL http://<server name>:8000/sap/bc/webdynpro/sap/ZGFS_JEWD/ call was terminated because the corresponding service is not available.
Note
The termination occurred in system FQ3 with error code 403 and for the reason Forbidden.
The selected virtual host was 0 .
What can I do?
Please select a valid URL.
If you do not yet have a user ID, contact your system administrator.
ErrorCode:ICF-NF-http-c:000-u:SAPSYS-l:E-i:lnxeccq1_FQ3_00-v:0-s:403-r:Forbidden
HTTP 403 - Forbidden
Your SAP Internet Communication Framework Team
Any help would be appriciated.
TIA
Amit
Edited by: Amit on Feb 1, 2010 2:38 PM

Hi,
When you transport your WebDynPro App to QA system or even Production, you need to manuallly activate the Service in transaction SICF.
goto SICF, execute for Hierarchy Type: "SERVICE" --> default_host->sap->bc->webdynpro->sap->
look for your Application Name here & right clik & Activate it.
your application will work fine then.
PS: If you donot have the authorization, have someone from Basis activate the Service.
Thanks,
Phani
Edited by: Phani Rajesh Mullapudi on Feb 1, 2010 7:36 PM

HTTP 500 internal server error while starting abap web dynpro application

Hi there,
i have some problems concerning my web dynpro abap configurations in the system. When i start an application the browser appears and displays the http 500 internal server error. The required icf nodes are activated, as far as i know. the following properties are set:
hostname: aet
port: 8000
The generated url for the web dynpro application looks as follows:
http://aet.ls3001:8000/sap/bc/webdynpro/sap/zwdr_test?sap-language=EN
Maybe anybody of you out there has an idea for that situation.
Thanks for your afford and kind regards,
Albert

Hi Ulli,
the error message says:
UNKNOWN HOST
Description: Unable to locate the server named "aet.ls3001" --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again.
So the problem is the hostname.
When i replace the hostname with the ip of the server, the following error occures:
COULD NOT CONNECT
Description: Could not connect to the server "10.18.187.9".
But with SAPLogon, its possible to connect on the server by filling in the ip adress.
Kind regards,
Albert

Get HTTPS URL for Web dynpro application

We are using SSL. By default the URL generated for the Web dynpro application is HTTP.
We went to SICF, and deactivated the HTTP service. That made the URL point to HTTPS.
But few problems started coming because of it:
- Our Content server became inaccessible.
- Every time server is re-started, we need to manually go and de-activate HTTP Service.
We even tried to set the parameter icm/icm/HTTP/redirect_0. But problem is not solved.
I know this question is asked before, but every time the answer is to read the help document on ICM.
What's the correct way for any webdynpro application to point to HTTPS? I don't think de-activating HTTP service is the right way.
Any suggestions please?
Thanks in adv.

Thanks a lot Thomas. I'd ask the Portal Admin to try it out.
There is another similar problem we are facing: I have embedded Webdynpro in R/3 screen. Then used the cl_gui_wdr_viewer class's load_application method passing HTTPS protocol.
It returns HTTPS URL only, but is not showing up on users' laptops.
Earlier we were not passing HTTPS protocol, so generated URL was HTTP, and it was not showing on users' screen (can show in ours). Reason we found out is that users' site has HTTP port blocked. They cannot show any HTTP url.
So we changed to get HTTPS URL, but that also gives the same problem. It is still trying to get HTTP url.
Here is the URL that the users got: (when they right click to see the URL generated)
res://ieframe.dll/dnserrordiagoff_webOC.htm#http://abc.def.jil:8000/sap/public/myssocntl?sap-client=220
Can give any clues on why this is going wrong? Cannot raise OSS as I know embedding Webdynpro in R/3 is not supported
Thanks in adv.

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

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 accesing ABAP web dynpro application

Hi Experts,
We are getting warning symbol on web page status bar, when we are accessing the ABAP web dynpro application
only first page of application is getting loaded and when we click on page it is showing error on status bar and we can perform any thing.
once we double click on warning icon,
below details are coming:
Line: 1491
Char: 3
Error: Object Expected
Code: 0
URL: url of the ABAP web dynpro application
This scenario is occuring for many ABAP WD application for a client.
Please guide how to solve this issue?
Thanks!
Piyush

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

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

Cannot deploy web dynpro applications

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

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

Source code for "Creating an Extended Web Dynpro Application"?

Hello!
I'm a rookie in the field of SAP Netweaver and I'm justing getting started with some tutorials. My problems with "Creating an Extended Web Dynpro Application" are to massive to be posted on this forum in this stage. What I want to have some help with is to find the source code for that tutorial so I can get som guidence from there.
Following text is cut out of this page:
http://help.sap.com/saphelp_nw70/helpdata/EN/5d/f42fef2eec724597a03b6bcc670c2c/frameset.htm
Creating an Extended Web Dynpro Application
You can download the Web Dynpro project for the current tutorial from the Software Developer Network SDN (http://sdn.sap.com -> Web Application Server -> Web Dynpro -> Sample Applications and Tutorials) in two versions: one skeleton version you can use for exercises and one final version (solution) for an immediate build, deployment and run on the Java engine of the SAP Web Application Server.
How hard I try I can't find the specific source code on sdn.sap.com
Does anyone have a clue where it is?
Thanks!
Best regards
/Johan Månsson Lindströ

Hi!
I did what you said but I seem to miss the IDE folder. This is what it looks in my Explorer
C: > Program Files > SAP > IDE > CE > eclipse > (no folder called "examples")
I also did a search in this eclipse folder for "examples" but I did'nt find the example I'm looking for
I am running a newer version of NWDS:
SAP NetWeaver Developer Studio
SAP NetWeaver 7.1 Composition Environment SP03 PAT0000
Maybe that's why things don't look the same?

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.

Reg: Closing and Opening Web Dynpro Application in same browser

Dear Experts
In my webdynpro application when i click a button another web dynpro application is opened in another window(another browser) .
But i want to open the second web dynpro application inside the same browser in which closing the first applicaiton and opening the second web application in same browser window .
Please guide me to do this.
Regards
Arun

hi ,
Exit plugs have the special property that they use the defined URL parameter. After you have created the URL parameter in the parameter list on the Outbound Plugs tab page in the window editor, you can specify a value for this parameter in the method that calls the exit plug.
ref
link:[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/ca3351508f04e7e10000000a42189c/content.htm]
it would help u
regards,
amit

How can I convert my Web Dynpro Application to Web Dynpro with GP Interface

Hi experts
I am trying to make my Web Dynrpo Application implement GP interface.
I encountered a question .
when I added GP interface controller, "Window" component also added automatically.
But I have already had a "Window" componet which contains alot of View settings.
Do I have to Use newly added GP "Window" component?
if so, do I have to recreate "Window" Componet whenever I convert to my web dynpro application implementing GP interface ?
Thanks in advance

Yes you have to use the automatically added window.
Check <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/50d74ada-0c01-0010-07a8-8c118d408e59">this</a> tutorial on how to implement a GP WD.
Regards,
Christophe

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

How To Consume UME services in Web Dynpro applications

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

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

Web Dynpro application - HTTP or HTTPs

Similar Messages

Maybe you are looking for