Defining + testing Web Service

Hi,
I've defined a web service from ID and loaded the WSDL into XML Spy and trying to SOAP request from the WSDL.
But I get the following error when I try to validate the WSDL.
Unable to locate a reference to a supported schema type (DTD, W3C Schema) within this document instance.
however I've the following XML tag in my WSDL
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="http://Webservice.com/xi/WS00" name="MI_AVG_OUT" targetNamespace="http://Webservice.com/xi/WS00">
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://Webservice.com/xi/WS00" targetNamespace="http://Webservice.com/xi/WS00">
I dont see the option 'Create new SOAP request' since the WSDL is not validated.
And another question..when I defined Webservice, I had to input Message interface twice
in 'Specify the Interface' step and (step 5 in <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm">help.sap.com</a>)
in 'Specify the Sender' step (step 7 in <a href="http://help.sap.com/saphelp_nw04s/helpdata/en/31/daa0404dd52b54e10000000a1550b0/content.htm">help.sap.com</a>)
What is the difference between these two...I mentioned my synchronous o/b interface MI_AVG_OUT and its namespace. Is that right?
Thanks in advance
praveen

I tried and tested the same WSDL using oxygen. It is working perfectly well.
I donno why XML spy was saying it as invalid, but I got what I wanted.

Similar Messages

Problem when defining a web service

Hello,
I have defined several BAPI that I am calling from an external application by exopsing those BAPI using the SOAP adaptor.
All goes well for all of them except one.
For the one having problems the Integrantion engine is routing that call to different webservice than the one I expect it to do it,
these are some of the paramenters I use when defining the web service in the Integration Builder:
Interface name: MI_BAPI_PPMSRVAPS_GETLIST
Communitcation chanel: CC_SOAP_BAPI_PPMSRVAPS_GETLIST
Address: http://sapxi:50000/xisoapadapter/messageservlet?channel=:BS_WEBSERVICE_GREYCON:CC_SOAP_BAPI_PPMSRVAPS_GETLIST
but instead when I test the generated wsdl using soapUI: the integration engine returns this error:
Canceled with Errors 02.06.2010 15:04:22 02.06.2010 15:04:23 [websericename] [namespace]MI_BAPI_PDSSRVAPS_GETLIST
My guess is that at some point I defined wrong the web service but I have no way to redefine it or revert how it was defined.
I redefined the webservice with correct parameters, but there is no change in behaviour.
I checked server address and port (it is the exact same of the other BAPIs that work)
Where can I see all defined web services when they are defined via the Integration builder define web service option?
How to delete a webservice published this way?
Any advise?
Any help is very much appreciated.
Regards,
Mauricio Pego

Hello there.
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
u2022 404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
u2022 Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
u2022 If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
u2022 If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
Try some of the recommendations that most apply to your case.
Hope it helps!
Regards,
Caio Cagnani

Error while executing Test Web Service

Hi,
I get an error while trying to test the web service deployed on Weblogic 10.3.1 through jdeveloper 11.1.1.1.0.
This simple web service is created by following the example in http://www.oracle.com/technology/products/jdev/11/cuecards111/j2ee_set_16/ccset16_ALL.html
After deploying the web service, the Test Web service Event in the Enterpise manager results in error. The error is as follows : -
The selected operation processRating could not be invoked.
An exception occured while invoking the webservice operation. Please see logs for more details.
oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException
+ java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: oracle.fabric.common.PolicyEnforcementException at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:570) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1245) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run+…………………………..
Has anyone encountered this error ?
Thanks.

HI,
RFc is not called becuase:
1. we tried RFC debuggin with proper user. it never stopped at break point.
2. TCODE: sxmb_moni in PI did not show any entry for incoming messages.
The import bindings are proper. We tried using .execute(1) , nothing happened.
We are able execute freely avaliable Web service but not the one exposed from PI.
Hence we feel their is problem between PDF and PI itself.
The user we put in the pop up is SERVICE USER. The PI consultant uses the same user and is able to execute but from PDF we are not able to execute.
We also tried with a DIALOG USER with same roles and authhorizations as the SERVICE USER. BUt still it did not execute.
Thanks and Regards,
Aditya Deshpande
Edited by: Aditya Deshpande on Nov 16, 2009 1:00 PM

Error in ejbCreate using a Test Web Service

Hi,
I'm new to the Bea and j2ee worlds and I'm following the steps of "Getting Started: Enterprise JavaBeans" in "Tutorials".
I've done "Step 4: Test the EJBs" but during the test (with a Test Web Service) these exceptions raised:
Exception in hello
javax.transaction.TransactionRolledbackException: Error in ejbCreate:: javax.ejb.EJBException: nested exception is: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/MyVisitBean in /app/ejb/MyEJBProject.jar#Hello.; remaining name 'comp/env/ejb/MyVisitBean'
javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/MyVisitBean in /app/ejb/MyEJBProject.jar#Hello.; remaining name 'comp/env/ejb/MyVisitBean'
javax.ejb.EJBException: nested exception is: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/MyVisitBean in /app/ejb/MyEJBProject.jar#Hello.; remaining name 'comp/env/ejb/MyVisitBean'
; nested exception is:
javax.ejb.EJBException: nested exception is: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/MyVisitBean in /app/ejb/MyEJBProject.jar#Hello.; remaining name 'comp/env/ejb/MyVisitBean'
Caused by: javax.ejb.EJBException: nested exception is: javax.naming.NameNotFoundException: While trying to look up comp/env/ejb/MyVisitBean in /app/ejb/MyEJBProject.jar#Hello.; remaining name 'comp/env/ejb/MyVisitBean'
... 46 more
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:897)
at weblogic.jndi.internal.ApplicationNamingNode.lookup(ApplicationNamingNode.java:150)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:256)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:359)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at hello.HelloBean.ejbCreate(HelloBean.java:27)
at hello.Hello_oztp1s_Impl.ejbCreate(Hello_oztp1s_Impl.java:135)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at weblogic.ejb20.pool.StatelessSessionPool.createBean(StatelessSessionPool.java:172)
at weblogic.ejb20.pool.StatelessSessionPool.getBean(StatelessSessionPool.java:110)
at weblogic.ejb20.manager.StatelessManager.preInvoke(StatelessManager.java:140)
at weblogic.ejb20.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:137)
at weblogic.ejb20.internal.StatelessEJBObject.preInvoke(StatelessEJBObject.java:69)
at hello.Hello_oztp1s_EOImpl.hello(Hello_oztp1s_EOImpl.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.bea.wlw.runtime.core.control.EJBControlImpl.invoke(EJBControlImpl.jcs:665)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
at helloControl.helloBeanCtrl.hello(helloBeanCtrl.ctrl)
at helloControl.helloBeanCtrlTest.hello(helloBeanCtrlTest.jws:22)
Everything has gone well until Step 3. I've done everything tutorial has said (ejb-local-ref, etc..) but it doesn't work.
Probably it's a stupid error, but I don't know where I have to look for.
Thank you and sorry, but I've never seen Bea Workshop!
m

Hi
You can use a java web service to publish a Web service from a Java class.
A wizard creates the WSDL document and deployment files needed to publish your code as a Web service. After you select the class and methods you want to publish, the wizard generates deployment descriptors, a JAX-RPC mapping file, and a WSDL document that can be deployed to an application server.
You can refer : \bpel\samples\tutorials\102.InvokingProcesses\ws sample to invoke a WS using JAX-RPC Call.
Hope that helps!
Cheers
A

Define a Web service in XI 7.1

How can I define a web service in PI 7.1 in SOAP adapter
Thanks

Hi
Go to the tools -> define web service
5 steps to follow-
Introduction
give the url of the web server
give the sender service name
give the message type
then overview, save the WSDL file.
Dheeraj Kumar

Why JDEVADF11.1.1.3 can not test web service in IE for Integrated WebLogic

Hi,
Testing a web service deployed to Integrated WebLogic Server.
1.When you deploy the web service to Integrated WebLogic Server, examine the contents of the log window. Find http://IP_address:port/Project1-context-root/MyWebService1
2.Copy the URL and paste it into browser. The browser shows a simple page which lists the operations available on the service.
3.Enter a parameter, and click Enter. The result from the web service is displayed.
My question:
Why only display Web Services Endpoint and Information . Can not have Enter a parameter and operations available on the service.
HttP analyzer test web service is OK.
Thanks

Hi,
That is because you are looking at the endpoint information.
If you want to test the service in a browser, then you can use the Weblogic Test Client.
When your Integrated WLS is running, point the browser to the following url: http://localhost:7101/wls_utc/
Thanks,
Vishal

Is it possible to test Web Service operation from Browser

Hi,
I'm new with Web Logic and Web Service.
Weblogic version: 10.3.5
SOAP Web Service with RPC/Literal message format
Created a Web Service and deployed that onto Web Logic.
Also managed to get the WSDL page. However, when i tried to invoke one of the method from a web browser, it gives me a 404 Error. Not found.
WSDL URL
http://localhost:7778/self_service-self_service-context-root/self_servicePort?WSDL
Method:
<WL5G3N0:operation name="trivialProc">
<WL5G3N3:operation soapAction="http://package/Self_service.wsdl/trivialProc"/>
<WL5G3N0:input>
<WL5G3N3:body use="literal" parts="String_1 Integer_2 String_3" namespace="http://package/Self_service.wsdl"/>
</WL5G3N0:input>
<WL5G3N0:output>
<WL5G3N3:body use="literal" namespace="http://package/Self_service.wsdl"/>
</WL5G3N0:output>
</WL5G3N0:operation>
Is it possible to test Web Service method through browser?
I used Web Service on OC4J previously, and I was able to test the method directly from a web browser.
Thanks
Regards,
Andi

you can test web service using testclient option in weblogic
for more information please check below link
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13952/taskhelp/webservices/TestAWebService.html
http://docs.oracle.com/cd/E13224_01/wlw/docs100/guide/webservices/WSTutorial/tutWebSvcStep4.html
Regards,
Sunil P

Alert: WebServices connectivity (Internal) transaction failure - The credentials can't be used to test Web Services.

Hi.
Could you please help me to resolve this issue.
I have SCOM 2012 installed to monitor environment with Exchnage 2010 SP3. There are 2 sites with Exchnage servers within the organization. There are 2 mailboxes being created to test both sites.
I am getting following alert:
Alert: WebServices connectivity (Internal) transaction failure - The credentials can't be used to test Web Services.
description: The test mailbox was not initialized. Run new-TestCasConnectivityUser.ps1 to ensure that the test mailbox is created.
Detailed information:
[Microsoft.Exchange.Monitoring.CasHealthUserNotFoundException]: The user wasn't found in Active Directory. UserPrincipalName: extest*****@****.local. Additional error information: [System.Security.SecurityException]:
Logon failure: unknown user name or bad password.
Diagnostic command: "Test-WebServicesConnectivity -MonitoringContext:$true -TrustAnySSLCertificate:$true -LightMode:$true"
EventSourceName: MSExchange Monitoring WebServicesConnectivity Internal
I have tried the next steps:
1. Verified that mailbox is exist and it's not locked (same for the second mailbox)
2. Deleted those mailboxes and created a new using new-TestCasConnectivityUser.ps1 verified that this mailbox is visible on all DC's accross the forest (both mailboxes)
and that temporary password was accepted;
3. Cleared the cache on the SCOM 2012;
4. Still getting the same alert
I will really appriciate any help.
Thanks.

Hi,
Hope these posts help you:
http://thoughtsonopsmgr.blogspot.ca/2013/11/exchange-server-2010-mp-no-synthetic.html
https://social.technet.microsoft.com/Forums/systemcenter/en-US/437f2bbb-cd96-40c3-8c56-6d4d176a9520/exchange-2010-mp-constantly-throws-webservices-connectivity-internal-transaction-failure?forum=operationsmanagermgmtpacks
Natalya
### If my post helped you, please take a moment to Vote as Helpful and\or Mark as an Answer

Load testing web service with JMeter

Hi,
Has anyone had success with using JMeter to load test Web Service generated by Jdev and deploy on iAS904?
Thanks,
Charles Li

hi
Calling user needs authorization object S_SERVICE
regards
afzal

Error on page when trying to test web service in EM

Hi,
I've developed a couple of web services in JDeveloper and tested them through Enterprise Manager. But the latest service won't work as expected. When I press "Test Web Service" for this particular port I get the message "Error on page" and
"Line: 94
Char: 1
Error: Object expected
Code: 0"
For the other web services the possible input parameters are shown as an HTML form and you can also choose to use an XML source. But this won't work in this case. No input parameters are shown and you can't choose XML source.
My question is of course the reason for this behaviour. And secondly; are the possible input parameters retrieved from the xsd file or from somewhere else? Could there be an error in it causing the problem? I'd be happy to provide some code, although right now I'm not sure which code snippet is appropriate.
Thanks in advance!
Kerstin

Update:
Now I see that there are in fact two error messages. The second one is the one presented above. But the first one says:
Line: 145
Char: 97
Error: Expected ';'
Code: 0
My question now is to what file it is referring?? Is it to ProjectAccountingPort.js that is automatically created? THen why is it not properly created??
Please, please help me with this! The deadline is in a few days...

HTTP 404 on ESB Test Web Service

Hi,
I cannot test my ESB service anymore cause, when i click on Test Web Service page of my Enterprise Manager, I receive an HTTP 404 error.
I can't see any error log which colud help my understand the reason for this.
Hoping it can help: this situation started few days ago, while i was trying to create an AQ JMS queue, modifying some configuration files like application.xml, jms.xml and data-sources.xml
I'll appreciate any kind of help

Hi,
I've figured out the cause for previous quoted problem:
in default-web-site.xml configuration file of /j2ee/home I've found a propery ohs-routing set to false.
In forum's thread "Use HTTPS to access webservice on standalone OC4J" that property wasn't set, so I removed it and magically now it works!
My question now is, which event caused such a change in default-web-site.xml file? How can I prevent or even controll it?
Thank you,
Lisa

Define External Web services in SPRO. in SRM

Hi SRM Gurus,
We are doing an Upgrade from SRM3.0 to SRM7.0 with MDM.
In SRM 7.0 -SPRO -We have to do the config in Define External Web services
What are the parameters to maintain.
I read from SDN that
Following parameters are not required in SRM 7.0. It was for ITS.
~OkCode ADDI
~target _top
~forcetarget yes
~caller CTLG
You need additional parameter in SRM 7.0.
returntarget _parent - for this what is the input parameters
Hi Masa /Muthu
Can you list down what are the Input parameters required for this config and the details?
Regards
G.Ganesh Kumar

Hi Masa,
We have deployed the SRM-MDM Catalog Search UI in Portal.
we tried accessing the http://<Portal Host>:<Portal Port>/SRM-MDM/SRM_MDM
Then we got a screen (Search UI App screen), where in we have provided the MDM Server name, then the MDM Server Password, then presses the Connect button, then below this, it displayed the Repository name created in the MDM. We have selected the Repository, then provided the Credentials of a User (Name: T_CORP) in MDM which has "Catalog Manager", and the "UI Configuration Manager" Roles. Please note that these Role names were created by us in MDM. Is it the right procedure or do we have any standard Roles delivered by SAP in MDM to map? If any standard Roles are available, where we need to check these.
Once the Credentials of MDM User is provided, and then selected the "Login" button.
Then we are getting the below error.
"java.lang.IllegalArgumentException: Table with Code 'null' does not exist in the repository 'Repository' or is one of the system table (e.g. Workflows) that is not exposed in repository schema"
Please clarify; we are not configuring any values in iViews. Where we need to do this, I mean name of the iView, and what values do we need provide generally? We are just running the Search UI App application; I don't think it is an iView, because the URL shows the Application name details, etc...
Please guide us, how to fix this Error.
Regards
G.Ganesh Kumar

Define external web services

Hello all,
We are running CCM 1.0.Have a doubt regarding "defining the external web services" in catalog content management.
In the documents it says " you must define external web services to define the connection to:
1.] CCM catalogs; 2.] OCI Catalogs
What is the difference between the two?? Are CCM catalogs not OCI compliant?
I always thought that once we load catalogs in CAT and CSE..that is it.What are these OCI catalogs now??
Please help
Sam

Sam,
I can help you to define external webservices -
You can define webservices using WF_EXTSRV.
You will have to enter service id, Log, Servers, and Port, specify your system access data for HTTP. You can get these details from your BASIS team. You will have to specify path for your BSP (Web Page).
Select the call mode as 'Dialog Based Services'.
After this you will have to define import/export parameters. Normally export parameters is a 'Decision' made by the user (Approved / Rejected).
You will have to maintain entry for your service id and Web task in table SWLWPTSSID. (Use SM30 to do it).
Hope these details will help you.
Regards.
Pras

Error when testing web service

Hello,
I published a web service in the Service Registry, and now I am attempting to test it out in the Web Services Navigator. Unfortunately when I click on the web service from the search results I get the following error:
while trying to invoke the method com.sap.esi.uddi.sr.api.ws.PhysicalSystemKeyType.getLogicalKey() of an object returned from com.sap.esi.uddi.sr.api.ws.ServiceDefinitionType.getPhysicalSystemKey()
Has anyone seen this before?

Hi ethan,
I guess problem with SLD/SR. Did you complete SLD & SR configuration steps?
Please see it: http://<host>:<port>/nwa -> Configuration Management -> Scenarios -> Configuration Wizard.
See if
1) Registering Services Registry instance in SLD
2) Services Registry Destinations Creation
are not initial .
Nikhil

Error while testing Web Service in WS Navigator

Hello again,
i'm trying to test the WSDL with WS Navigator from the Webservice ECC_PURCHASEREQUESTCRTRC created with ECC.
It finds the WSDL, i can insert parameter but the result is this Error:
Web-Service returned error. error code: "(http://schemas.xmlsoap.org/soap/envelope/)Server" error string: "Error during proxy processing"
so what went wrong?

The Log says that:
Server Exception: Error during proxy processing; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
[EXCEPTION]
java.rmi.ServerException: Server Exception: Error during proxy processing; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.processFault(SOAPTransportBinding.java:1962)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1360)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP_Idenpotency(SOAPTransportBinding.java:969)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:950)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:907)
at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DInterfaceInvokerImpl.invokeOperation(DInterfaceInvokerImpl.java:76)
at com.sap.esi.esp.wsnavigator.lib.Operation.execute(Operation.java:171)
at com.sap.esi.esp.wsnavigator.WSNavigator.fireExecuteCurrentOperation(WSNavigator.java:600)
at com.sap.esi.esp.wsnavigator.wdp.InternalWSNavigator.fireExecuteCurrentOperation(InternalWSNavigator.java:310)
at com.sap.esi.esp.wsnavigator.ResultView.onPlugFromLogoView(ResultView.java:1219)
at com.sap.esi.esp.wsnavigator.wdp.InternalResultView.wdInvokeEventHandler(InternalResultView.java:491)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:142)
at com.sap.tc.webdynpro.progmodel.window.ViewController.invokeInboundPlugHandler(ViewController.java:446)
at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.processInboundPlugQueue(NavigationManager.java:305)
at com.sap.tc.webdynpro.clientserver.cal.NavigationManager.navigate(NavigationManager.java:320)
at com.sap.tc.webdynpro.clientserver.phases.NavigationPhase.execute(NavigationPhase.java:63)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:514)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:55)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1652)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1466)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessingStandalone(ApplicationSession.java:884)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:856)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:343)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:315)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:76)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:359)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:476)
at com.sap.tc.webdynpro.serverimpl.wdc.ForwardServlet.doPost(ForwardServlet.java:63)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:400)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:203)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:438)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:427)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:80)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:268)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
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:78)
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:78)
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:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:54)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.SOAPFaultException: Error during proxy processing
at com.sap.engine.services.webservices.espbase.client.bindings.impl.FaultUtil.buildFaultException_SOAP11(FaultUtil.java:220)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.FaultUtil.buildFaultException(FaultUtil.java:65)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.processFault(SOAPTransportBinding.java:1924)
... 73 more
Datum:     Single Click Filter by Datum     2011-01-18
Zeit:     Single Click Filter by Zeit     09:39:05:734
Kategorie:     Single Click Filter by Kategorie     com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
Ort:     Single Click Filter by Ort     com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding
Applikation:     Single Click Filter by Applikation     sap.com/tcesiespwsnavui
Thread:     Single Click Filter by Thread     Thread[HTTP Worker [@18923517],5,Dedicated_Application_Thread]
Datenquelle:          j2ee\cluster\server0\log\defaultTrace_00.trc
Argumente:
DSR-Transaktion:     Single Click Filter by DSR-Transaktion     41dd215022de11e08794000c2952e027

Defining + testing Web Service

Similar Messages

Maybe you are looking for