Serialization error in SAP Web Service.

Hi all,
I have exposed a custom RFC as a Web Service. This is a simple web service that returns Customer Data (from kna1) based on the Customer ID which we provide as input.
In the RFC, I have declared an internal table (G_RET) in the tables section of the RFC.
Now, while testing the web service, I can see a check box with NULL option beside the G_RET. If i check the NULL option for G_RET, I get an error.
XML Serialization Error. Array Property [Item] in class [none] must not have NULL elements. This is restricted by schema description.
This is a high priority task. Please reply to me with any solution that you may have.
Regards,
Preksha.

Your problem has nothing to do with SAP web service. When you expose a RFC function as a web service, you are defining a service contract using WSDL technologies and XML message format enforced by the schema definition associated with the data source.
When a system consume a web service it is upto that system to provide a client framework so that it can provide an implementation enforces by the WSDL contract. Contract terms in WSDL is only applicable to data types, message types, access style and ecoding.
It is upto the client framework to provide a mechanism to send and receive the data as per the contract.
In your case, you are using a Microsoft client, so MS implementation of web service technology play a big role here.
C# XML serialization class from the MS client program you are using to call the program, read the WSDL contract and try to understand the definition and terms and conditions of the messages, types, binding.
In your WSDL you may have constraints applied at each field level of the schemas associated with the input and output messages of the web service methods.
Unfortunatly the way C# XML serialization class understand the terms and condition is confusing and it create a rum time error.
Having said this all stories now let us get into practical way.
1. Test ur web service using a non MS client
2. Make sure it is working, this isolate your issues to the way client understanding the WSDL contracts.
3. Then work with some MS guys in your shop to address this issue.
From your post I hope you are a candidate having experience in working with SAP customization project. However when ever you deal with open technologies such as JAVA, Web Services, it is highly recomended to think outside the BUNN.
AS SAP move towards more open technologies such as JAVA, WSDL, SOAP, WS, XML, XSD it is very important to elaborate your knowledge beyond the scope of a customization project.
Thanks

Similar Messages

  • SOAP Response Version Mismatch error with SAP web service

    My company just recently upgraded to SAP CRM 7.
    The old way of creating web services in SAP worked fine, but now, there is something a bit off with SAP.  When I call the web service the send returns a Fault Event with the error : SOAP Response Version Mismatch
    I had a simple web service created with only 1 text input and 1 text output to make sure that it wasn't the parameters or return type.  I got the same error.
    Searching on the forum or the web hasn't provided with any good answer to the issue.
    Any thoughts on this?

    Problem solved

  • How To Debug XML Serialization Error while deploy web services

    <b>My Scenario</b>
    I've created a Java Projects with a Class. From there I convert it to Web Service by creating the virtual interface, the web services definition and the web service configuration. After that I deploy to the SAP WAS (SP11). At this instant I only try to deploy the web services with the intension to modify it later for GP to invoke.
    <b>Result</b>
    When deployment the Web Service I get an XML Deserialization error. Error text is below.
    <b>Question</b>
    How do I go about debugging this? What logs are good starting point? Can I capture the entire SOAP response message somehow?
    Thanks
    <b>
    Error Test</b>
    Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
                              at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
                              at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
                              at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
                              ... 27 more
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:681)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: java.lang.Exception: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to update web services for application sap.com/TimeoffService. . Additional info: none
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:164)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:118)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:86)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateManager.makeUpdate(WSUpdateManager.java:52)
                              at com.sap.engine.services.webservices.server.deploy.WSDeployer.makeUpdate(WSDeployer.java:274)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.makeComponents(UpdateTransaction.java:400)
                              at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
                              at com.sap.engine.services.deploy.server.application.UpdateTransaction.begin(UpdateTransaction.java:164)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
                              at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.update(DeployServiceImpl.java:669)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
                         Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices deployment exception! The reason is: Error occurred, trying to generate web services deployment files for application sap.com/TimeoffService. . The error refers to application: none, jar: , web service: .
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:296)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.deployWebServices(WSUpdateProcessor.java:262)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.updateWebServices(WSUpdateProcessor.java:155)
                              ... 21 more
                         Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, parsing com.sap.engine.services.webservices.server.deploy.descriptors.sapwebservices.WSDescriptor descriptor, application sap.com/TimeoffService, web service timeoffServiceConfig, location message: type: jar file, location: E:\usr\sap\SIC\DVEBMGS01\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1186995503687\TimeoffService.wsar . . Additional info:
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:907)
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebService(WSDefinitionFactory.java:176)
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.loadWebServices(WSDefinitionFactory.java:158)
                              at com.sap.engine.services.webservices.server.deploy.ws.update.WSUpdateProcessor.generateDeployFiles(WSUpdateProcessor.java:284)
                              ... 23 more
                         Caused by: com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException: Webservices common deployment exception! The reason is: Error occurred, trying to parse source type: zip entry, zip file location: E:\usr\sap\SIC\DVEBMGS01\j2ee\cluster\server0\.\temp\deploy\work\deploying\reader1186995503687\TimeoffService.wsar, entry: dsta/timeoff/test/business/TimeoffServiceVI.videf . Additional info:
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:925)
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseWSDescriptor(WSDefinitionFactory.java:817)
                              ... 26 more
                         Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. XML Node [VirtualInterface.Functions][http://xml.sap.com/2002/10/metamodel/vi] have minOccurs>0 in schema definition but is missing in node [VirtualInterface][http://xml.sap.com/2002/10/metamodel/vi].
                              at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType._loadInto(GeneratedComplexType.java:1197)
                              at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:945)
                              at com.sap.engine.services.webservices.server.deploy.descriptors.vi.VInterfaceParser.getVInterface(VInterfaceParser.java:46)
                              at com.sap.engine.services.webservices.server.deploy.ws.WSDefinitionFactory.parseVI(WSDefinitionFactory.java:920)
                              ... 27 more
                              at com.sap.engine.interfaces.webservices.server.deploy.WSDeploymentException.writeReplace(WSDeploymentException.java:64)
                              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 java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
                              at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1011)
                              at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)
                              at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)
                              at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)
                              at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
                              at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
                              at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:144)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:322)
                              ... 8 more

    Hi Paul..
       This is a common problem when you are working with webservices, i have worked with them and not always the response of the ws comes like de wsdl says, depends of your wsdl provider.
       I suggest you that checks your response of your webservice with the Enterprise Portal Web Services Checker View
      For see this view in NetWeaver go to Window > Show View > Other > Enterprise Portal Web Services Checker
      Put the wsdl url definition in wsdl url textbox
    and the click in the letter W, this procedure brings you all methods and everything for play with the WEB Services.. and you can check the response of you webservices call funtion, checks that all the tags comes like says in the wsdl
    Good luck
    Joshua

  • Serialization error when calling web service method

    Hi,
    In JDeveloper 10.1.3.1, I'm working on an EJB that will be deployed as a web service. There is a method in the EJB that is defined to return a generic Object, but in the implementation, it really returns one of several possible specialized bean objects. I can deploy the EJB successfully to IAS 10.1.3.1.
    I created a web service proxy from the wsdl that was generated from deploying the EJB. Using the proxy, I try to call the EJB method and cast the method's return value to the bean object I know should be returned. However, I get an error like this:
    java.rmi.ServerException:
    start fault message:
    Internal Server Error (serialization error: no serializer is registered for (class com.test.TestBean, null))
    :end fault message
    Does anyone know how this serialization error can be resolved? If I change the web service method signature to return the bean object that is actually being returned (instead of Object), then it works fine. But I want to be able to define the method to return a generic Object because I plan to make the method flexible enough to return several different types of bean objects. Whenever the client calls the method, it will know what is the actual object being returned and I had planned to cast the return value to its actual class.
    Thanks for any ideas.

    Well, I think so... I've followed all the steps, and my merged WSDL file seems like the one in page 12...
    Any suggestion, please?
    Thank you,

  • SAP Web Service error text : The database returned a value containing an error , type  CX_SY_OPEN_SQL_DB

    Hello Guru's,
    we are creating sales order in SAP from a quote created in .NET,  through Web Service created in SAP, and consumed in .NET.
    When ever a order is created in SAP for a given quote, SAP returns the sales order number to .NET.
    Orders are getting created as expected, but once in a while we are getting the following error from webservice :
    Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    But the problem is order is getting created in SAP for the perticular quote for which we are getting the above error and this order number is not getting returned to .NET.
    Upon analysis in TCODE  SRT_UTIL for the above transaction ID, has the following details , which are hardly help full to resolve the error.
    ----TYPE                                  CX_SY_OPEN_SQL_DB
    ----ERROR_TEXT                   The database returned a value containing an error
    ----CX_SY_NO_HANDLER
    -----CLASSNAME                     CX_SY_OPEN_SQL_DB
    This Exception raised by Web Service application
    Could you please help in resolving this issue or alteast provide an approach for the same.
    Thank you,
    Suresh.

    Thank you Bhaskar,
    How can we clarify whether the error is from SAP or Web part.
    I have checked ST22, but there is not entry for the perticular  exception transaction ID
    My exception time stamp is
    -------------------START-------------6/9/2014 1:34:33 PM
    Error :Web service processing error; more details in the web service error log on provider side (UTC timestamp 20140609173429; Transaction ID 4DFCEFE33301F1EBB5CE00155D0B4530)
    -------------------END-------------6/9/2014 1:34:33 PM
    In al11, i found the following for the perticular exception time stamp
    **** Trace file opened at 20140609 133431 Eastern Daylight Time, by disp+work
    **** Versions SAP-REL 720,0,500 RFC-VER U 3 1442251 MT-SL
    XRFC> Begin of user trace
    XRFC> ---------------------------------------------------------------------
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - header                                         <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> REQ_SIZE   : 2685                                                   <
    XRFC> RESP_SIZE  : 0                                                      <
    XRFC> PARENT_ID  : ROOT_CALL_ID                                           <
    XRFC> TRC_KEY    : 40FCEFE3BD6EF184B5CE00155D0B4530                       <
    XRFC> REQ_BASED  :                                                        <
    XRFC> SESSION_ID : 0003925540FCEFE3BD6EF17DB5CE00155D0B4530               <
    XRFC> TS_CALL    : 20140609173408.2880000                                 <
    XRFC> SY_UNAME   :                                            <
    XRFC> HOSTNAME   :                                              <
    XRFC> SY_SID     : PRD                                                    <
    XRFC> SY_MANDT   : 300                                                    <
    XRFC> SYS_NR     : 19                                                     <
    XRFC> APPLSERVER :                                      <
    XRFC> ISPRESCHED : X                                                      <
    XRFC> DURATION   : 21810                                                  <
    XRFC> NETHDRTIME : 21810                                                  <
    XRFC> CALL_STATE : 2                                                      <
    XRFC> ERRORTYPE  : APPLFAIL                                               <
    XRFC> ERRORAREA  : APPL                                                   <
    XRFC> CTXDP_TYPE : SOAP_RUNTIME                                           <
    XRFC> SYNC_ASYNC : S                                                      <
    XRFC> LOCATION   : P                                                      <
    XRFC> DIRECTION  : I                                                      <
    XRFC> REQ_ID     : 91C57815916E421CA9F3D652FFACE9C7                       <
    XRFC> RESP_ID    : 00155D0B45301EE3BBFF89A0267EB5CE                       <
    XRFC> MSG_STATE  : 114                                                    <
    XRFC> IF_NAME_I  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> IF_NS_E    : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> IF_NAME_E  : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> ISSHORTCUT :                                                        <
    XRFC> TRC_PATT   : WSTEST                                                 <
    XRFC> TRC_SSID   : PRD_19                                                 <
    XRFC> TRC_USER   :                                           <
    XRFC> TRC_TS     : 20140609173409                                         <
    XRFC> TRC_COUNT  : 99                                                     <
    XRFC> TRC_EXT    :                                                        <
    XRFC> COMPLETE   : OK                                                     <
    XRFC> CALLEDPROG : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> SOAP_APPLI : urn:sap-com:soap:runtime:application:rfc:710           <
    XRFC> CONF_ID    : 00155D0B45301EE3AEFDAD78756555CE                       <
    XRFC> BIND_ID    : 00155D0B45301EE3AEFDAD787565B5CE                       <
    XRFC> OP_NAME    : ZsdCsCreateSalesorder                                  <
    XRFC> COMM_PATRN : Method:ZsdCsCreateSalesorder                           <
    XRFC> OP_NS      : urn:sap-com:document:sap:soap:functions:mc-style       <
    XRFC> REMADDRESS : 172.16.11.43                                           <
    XRFC> DT_OBJ     : ZSD_CS_CREATE_SALESORDER_SERVI                         <
    XRFC> MEMCONSUMP : 296291                                                 <
    XRFC> WSHOST     :                                                        <
    XRFC> WSPORT     :                                                        <
    XRFC> WSPROT     :                                                        <
    XRFC> WSCLIENT   :                                                        <
    XRFC> WSPATH     :                                                        <
    XRFC> PXYHOST    :                                                        <
    XRFC> PXYPORT    :                                                        <
    XRFC> USEDRFCDES :                                                        <
    XRFC> BONAME     :                                                        <
    XRFC> PROCCOMP   :                                                        <
    XRFC> DEPLOYUNIT :                                                        <
    XRFC> ------------------------------------------------------------------  <
    XRFC>                                                                     <
    XRFC> TRACE SOAP RUNTIME - trace records                                  <
    XRFC>                                                                     <
    XRFC> ------------------------------------------------------------------  <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING Exception handling for IF "ZSD_CS_CREATE       <
    XRFC> _SALESORDER_SERVI" OP name "ZsdCsCreateSalesorder" MSG ID           <
    XRFC> "91C57815916E421CA9F3D652FFACE9C7" user "STULZWEBSERV"              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7240000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SOAP_ROOT : An exception has occurred. |    <
    XRFC> program: CL_SOAP_RUNTIME_ROOT==========CP include: CL_SOAP          <
    XRFC> _RUNTIME_ROOT==========CM004 line: 120                              <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_NO_HANDLER : An exception with the type  <
    XRFC> CX_SY_OPEN_SQL_DB occurred, but was neither handled locally, nor    <
    XRFC> declared in a RAISING clause | program: SAPLSTXD include: LSTXDFDB  <
    XRFC> line: 200                                                           <
    XRFC>                                                                     <
    XRFC>                                                                     <
    XRFC> E SOAP_RUNTIME 20140609173429.7400000 : CL_SOAP_RUNTIME_SERVER      <
    XRFC> ->EXECUTE_PROCESSING CX_SY_OPEN_SQL_DB : The database returned a    <
    XRFC> value containing an error | program: SAPLSTXD include: LSTXDFDB     <
    XRFC> line: 227                                                           <
    XRFC>                                                                     <
    XRFC> ---------------------------------------------------------------------
    XRFC> End of user trace

  • Calling SAP Web Service from BPEL

    Hi
    I am trying to call a SAP Web Service friom BPEL using the SAP WSDL.It requires a basic authentication (Username/Password) which i am providing as partnerlink properties in bpel.xml.
    While testing the BPEL Process from the console, it is giving me an error
    "<summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Bad response: 401 Unauthorized</summary>"
    But when i am testing it from SOAP UI tool it is giving me the desired response.
    Does anyone has any idea why it is failing from BPEL?Is there any configuration which i am missing?
    Regards
    Ayush

    HI Ayush / Suryaveer..
    I am stuck at the same situation, trying to invoke a secured SAP webservice. The invoke fails with a security previlege exception.
    Am using the basicHeaders property to propagate the credentials to the SAP system.
    Can you please suggest on the same.
    credential propagation in bpel.xml :
    <property name="basicHeaders">propagate</property>
    <property name="basicUsername">ABC</property>
    <property name="basicPassword">DEF</property>

  • Error activating a web service based datasource ( BI 7.3)

    Hi,
    While activating a datasource based on web services i get the below error:
          "Internal error while deleting web service"
           "Error when activating datasource"
    As per one of the posts, we need to activate the services listed under "bc" ( path : virtualhost->sap->bc ) in tcode: SCIF.
    There are many services listed under the "bc" node that are inactive. Please let me know which are the services that needs to be activated under this node.
    Alternatively pls also suggest if there is any other way to solve this issue.
    Thanks.

    Hi Jayanthi,
    Please get help from Basis Team.
    Regards,
    Kuldeep Jain

  • Consuming a sap web service via jde 4.5.7 (ecc 6.0)

    Hi all,
    I have a question here, if u could help me, i have to call a sap webeservice via jde , but before i test a jde example by calling a public web service which is not a sap web service , i used to  give  url  as:
    connThread.get("http://www.webservicex.net/globalweather.asmx/GetCitiesByCountry?CountryName="Morocco;deviceside=true";
    i was not obliged to set the apn parameters and it does work
    here as it's mentioned , there is the access point, getcities ...  the method  name and the parameter name and the parameter value
    "Morocco", but i m asking how did we precise the methods  of an rfc sap, and the name parmeter and his value.
    have u any idea to help me understand how we call sap rfc, method name, parmaeter name, cz i m a newbie to sap and bb.
    but now when i try to call an rfc sap , i give the link
      connThread.get("http://hca-ecc.hca.group:8000/sap/bc/srt/wsdl/sdef_Z_WS/wsdl11/ws_policy/document?sap-client=800;deviceside=true;apn=hca-ecc.hca.group;tunnelauthusername=forma02;tunnelauthpassword=hcaforma" );
    but it's always giving me transmission failed without any error that may help me when debugger run.
    Thakx in advance.

    Hello Merry,
    Have you tried searching 'blackberry' in SDN. I found following and many more links. It gives me impression that you may have to use MDS and also may be SAP Webdynpro technology for UI rendering.
    blackberry integration with Mobile Infraestructure
    There seems to be special site from blackberry for SAP integration (free registration).
    https://www.blackberry.com/CorpDevZone/download/SAP/sap.shtml
    Re: Steps to show data on actual Blackberry :) Urgent please....
    Hope this will give you some headway in resolving your issues.
    Regards,
    Vandana.

  • How to publish a SAP Web Service in SAP XI/PI 7.0

    Hi,
    First I've to say that I'n new in this deals with SAP Web Services and SAP XI/PI.
    I've created a Web Service with TX SE80 using a standard BAPI.
    I've created the Client Proxy with TX SE80.
    I've created a Logical Port wiht TX LPCONFIG.
    I've tried this is SOAMANAGER but I have this error...
    "SRT Framework exception: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL"
    I would like to publish this service in my SAP XI/PI 7.0
    How can I solve the error in SOAMANAGER?
    How can I publish de SAP WS that I've created in SAP XI/PI?
    Thanks a lot.
    Waiting for your news.
    Fernando.

    Hi Dimitri,
    I had the same problem:
    "SRT Framework exception: Uninstantiated object "subject sidl service" in method IF_SRT_WSP_CONFIG_SIDL~CREATE_CLNT_CFG_FROM_WSDL_D of class CL_SRT_WSP_CONFIG_SIDL"
    And by following Nags hints I got solution:
    1, On the system where is your service provider, run transaction SICF
    2, Execute this transaction
    3, Go to node: default_host/sap/bc/srt/wsil
    4, Right click on "wsil" -> choose "Test service" - web browser should open with XML definition of service
    5, Find your service provider. In my case it looks like this:
    <service>
    <name>ZTEST_WS</name>
    u2212
    <wsdlNamespace>
    urn:sap-com:document:sap:soap:functions:mc-style/service
    </wsdlNamespace>
    <wsdlName>service</wsdlName>
    u2212
    <wsdl>
    http://xxx.yyy.com:8000/sap/bc/srt/wsdl/srvc_DF838C999AA282F18829001CC4D74176/wsdl11/service/ws_policy/document?sap-client=800
    </wsdl>
    </service>
    5, Look for WSDL link -> in my case:
    http://xxx.yyy.com:8000/sap/bc/srt/wsdl/srvc_DF838C999AA282F18829001CC4D74176/wsdl11/service/ws_policy/document?sap-client=800
    I dont know why, but this link is different like WSDL link in service definition which I can see in SE80:
    http://xxx.yyy.com:8000/sap/bc/srt/wsdl/sdef_ZTEST_WS/wsdl11/ws_policy/document?sap-client=800
    6, Use this link (from "wsil") instead of link from SE80 in SOAMANAGER to create logical port
    7, Yours logicall port should be created without errors.
    My question - have anybody idea, why this links are different and why only that second one works?
    Peter

  • Consuming SAP web services with tables

    I'm doing kind of feasibility study on consuming SAP web
    services from CF.
    So far so good, but I'm stuck dealing with tables
    (import/export parameters in SAP world).
    I know how to receive a table object from SAP functions:
    * With Apache Axis v1.2: pass an empty CF structure as a
    parameter
    * With Apache Axis v1.4: pass an empty CF array as a
    parameter
    Then the parameter is filled with data (replaced with Java
    object) and we can just parse the object accordingly.
    My question here is whether or not we can pass a *table with
    actual records*.
    For example, I want to pass a table with multiple records to
    update DB records under SAP.
    I tried passing (1) CF array of structure and (2) Java
    ArrayList with no chance.
    The web service call itself completes without errors (no
    method signature error), but the SAP function seems to see the
    parameter as an empty table.
    Anyone has been successful with this case?
    Any suggestion would be much appreciated.

    Thanks Dan,
    Unfortunately CF query object didn't work either.
    Now I'm looking at the code generated by Flex Builder to see
    how the classes are like ;-)
    It's just an ArrayCollection of simple value objects
    (representing a row).
    So CF array of structure or Java ArrayList looks a reasonable
    approach though they don't at all.

  • Errors when processing web service call

    Hello Experts,
    Based on a requirement, I got a URL based on WSDL, using which I created a Consumer Proxy in SAP.
    I created a Logical Port in SOA Manager with type selected as 'WSDL'.
    When I'm trying to execute the proxy class to call the webservice using the logical port through SE80  it is throwing an error log as stated below.
    1) SOAP:14 Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    2)Error when processing Web service call
    3)Error when calling SOAP Runtime functions: Unexpected element -el=definitions ns=http://schemas.xmlsoap.org/wsdl/
    Kindly help me out.
    Thanks,
    Vamshi

    Hi,
    Check Anton's reply in this thread: External WS Consumption Issue
    Also refer the below doc which may help you: Consume an External Web Service in a Nutshell with Good Old ABAP
    Calling WebServices from ABAP via HTTPS
    Regards,
    Kiran

  • Error consuming a web service

    I invoke a SAP web service from oracle with SOAP message
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    <soapenv:Body>
    <paem:ReadEmployeePersonalDataRequest xmlns:paem="http://nga/fer/paem">
    <HeaderMsgReq>
      <functionalId>Str 1</functionalId>
      <messageId>Str 2</messageId>
      <timeStamp>2005-12-31T23:59:59Z</timeStamp>
      <consumerApp>Str 3</consumerApp>
      <consumerUsr>Str 4</consumerUsr>
      </HeaderMsgReq>
    <BodyMsgReq>
    <Employee>
      <employeeCode>1001</employeeCode>
      </Employee>
      </BodyMsgReq>
      </paem:ReadEmployeePersonalDataRequest>
      </soapenv:Body>
      </soapenv:Envelope>
    SAP response with this  XML
    <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
       <soap-env:Header/>
       <soap-env:Body>
          <soap-env:Fault>
             <faultcode>soap-env:Server</faultcode>
             <faultstring xml:lang="en">WSRM:NH/WSRM: Consumer sent message for operation of type "asynchron reliable" without WS-RM sequence header/Language of error reason =E/Client =100/Location =Receiver/Class =CL_SOAP_WSRM_PROTOCOL/Method =WSRM_CHECK_SID_MNR_BEFORE_PRE/Use =WSRM: Consumer sent message for operation of type "asynchron reliable" without WS-RM sequence header/Sequence ID =/Persistent ID =3205FB4D72399977E10000000A340566/Message number =0 /Error key =5 /Error key name =wsrm/Namespace =http://schemas.xmlsoap.org/ws/20//WSRM:NH/WSRM: Consumer sent message for operation of type "asynchron reliable" without WS-RM sequence header/Language of error reason =E/Client =100/Location =Receiver/Class =CL_SOAP_WSRM_PROTOCOL/Method =WSRM_CHECK_SID_MNR_BEFORE_PRE/Use =WSRM: Consumer sent message for operation of type "asynchron reliable" without WS-RM sequence header/Sequence ID =/Persistent ID =3205FB4D72399977E10000000A340566/Message number =0 /Error key =5 /Error key name =wsrm/Namespace =http://schemas.xmlsoap.org/ws/2005/02/rm/Other information =/Other information =/Node name =http://schemas.xmlsoap.org/ws/2005/02/rm/Role =http://schemas.xmlsoap.org/ws/2005/02/rm</faultstring>
             <faultactor>http://schemas.xmlsoap.org/ws/2005/02/rm</faultactor>
             <detail/>
          </soap-env:Fault>
       </soap-env:Body>
    </soap-env:Envelope>
    If we change the invocation header section and remove the return carriage SAP responses correctly
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    </soap:Header>
    <soap:Header xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"></soap:Header>
    I don't find some notes of patches for SAP
    Thanks

    Hello,
    what is the version of SAP_BASIS ? Your example is so called Plain SOAP call. And if you have not very young patch, SAP basis supports only WS-RM for asynchronnous calls, which is something different.
    More can be found on wikis, e.g. http://wiki.sdn.sap.com/wiki/display/ABAPConn/Plain+SOAP.
    Rgds
    Tomas

  • Problem using an SAP Web service??

    Hi I am currently trying to use a Web Dynpro interface to link into an SAP Web Service and search for some data. However this is not working at the moment as I believe there is an issue with my system landscape and i don't know how to resolve it. I get this error:
    Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for web service mass config parameters service reference ID 'ac92ed3a-770d-428f-8b89-3dd26332b858' and application name 'demo.sap.com/poc2'. Check mass configuration has been done properly.
    I already had this issue when I was trying to create a web dynpro interface of a web service that i had created. I did solve that issue however then when i published that project The data was not within the table. I am now trying this as I did not seem to be getting a reply to my previous thread which is here:
    Re: Cannot get Web Dynpro app to work??!
    Ok so now I have started this new project just to see weather it was the web service that was the issue. However when i publish this project i get the error. The things I have tried are below:
    1. Going to the NWA of the server and going to SOA Management --> System Connection and then setting up a new connection with these settings:
    General
    System Type:                                        ABAP
    System Name:                                       HU2
    DB Host:                                                iwdf4158
    Client:                                                    800
    Installation number:                               0120003411
    Connectivity
    Services Source:                                 WSDL
    URL:                                                     http://sr.esworkplace.sap.com:80/ServicesRegistrySiService/ServicesRegistrySiPort
    Username:                                            sruser
    Password:                                           eswork123
    then from this I then tried to apply this connection to my project by going to NWA of the server and going to SOA Management --> Application and Scenario Communication --> Application Communication then I selected my project and added the provider system I had just set up as i presumed with me using a web service from SAP I would have to do this.
    I then tried adding another provider system which was the local server that the instance is installed on.
    Edited by: anixan on Apr 15, 2010 2:31 PM

    Hi Experts,
    I have found that the particular web service that I amusing is running from sr2.esworkplace.sap.com is there any way to find the settings of how to set this up in the Destination Template Manager of my server in order for the app to work. I would appreciate any help that can be offered. Thanks

  • Error calling external web service over HTTPS

    Hi everyone
    I'm trying to call an external web service over HTTPS, and continually get the following error:
    com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException: Peer sent alert: Alert Fatal: handshake failure
    I haven't tried doing this before, so not quite sure where to start. I have a client certificate that must be used to access the remote web service, and I think the problem is associating the client cert with the web service call.
    Has anyone else tried this before? Any suggestions of where to look?
    I've had a brief look at Key Storage in NWA, but it's not something I'm familiar with - so not sure if it's even the right place to be looking.
    Some help on this would be great!
    Thanks
    Stuart

    Thanks Aleksandar
    Here's the output from the trace. Unfortunately the SAP forums don't allow attachments, so it may be difficult to read. Please let me know if you see anything that may help.
    Thanks
    Stuart
    Time Severity User Thread Location Message
    09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:23:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@fa1b67
    09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:24:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@4c8af
    09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:24:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@b6981b
    09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:25:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:25:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:26:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' are configured '10.|127.|192.168.*'.
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider [com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider] 'nonProxyHosts' default value is '10.|127.|192.168.*'.
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Loadin mapping file from location :[c:/mapping.txt]
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider Additional file for CTS configuration can not be found [c:\mapping.txt (The system cannot find the file specified)].
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider >>>>>>>>> ERROR: Could not find mapping for service QName=vipSoapInterfaceService, class=class com.verisign._2006._08.vipservice.VipSoapInterfaceService
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Creating client instance with WSDL URL [https://pilot-vipservices-auth.verisign.com:443/prov/soap/val/soap] (vipSoapInterfaceService) <com.verisign._2006._08.vipservice.VipSoapInterfaceService>
    09:18:26:203 Debug Administrator HTTP Worker [0] ~es.espbase.client.jaxws.cts.CTSProvider com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider: Using SAP JAX-WS Implemetation to create service delegate.
    09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:26:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@5586b0
    09:18:26:687 Path Administrator HTTP Worker [0] ~s.espbase.wsdl.exceptions.WSDLException Exception : Peer sent alert: Alert Fatal: handshake failure
    java.lang.Exception
    at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1230)
    at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:147)
    at com.sap.exception.BaseException.<init>(BaseException.java:89)
    at com.sap.engine.services.webservices.espbase.wsdl.exceptions.WSDLException.<init>(WSDLException.java:34)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:140)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
    at javax.xml.ws.Service.<init>(Service.java:57)
    at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
    at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
    at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
    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:309)
    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: org.w3c.www.protocol.http.HttpException: Peer sent alert: Alert Fatal: handshake failure
    iaik.security.ssl.SSLException: Peer sent alert: Alert Fatal: handshake failure
    at iaik.security.ssl.r.f(Unknown Source)
    at iaik.security.ssl.x.b(Unknown Source)
    at iaik.security.ssl.x.a(Unknown Source)
    at iaik.security.ssl.r.d(Unknown Source)
    at iaik.security.ssl.SSLTransport.startHandshake(Unknown Source)
    at iaik.security.ssl.SSLTransport.getOutputStream(Unknown Source)
    at iaik.security.ssl.SSLSocket.getOutputStream(Unknown Source)
    at org.w3c.www.protocol.http.g.markUsed(Unknown Source)
    at org.w3c.www.protocol.http.HttpBasicServer.getConnection(Unknown Source)
    at org.w3c.www.protocol.http.HttpBasicServer.runRequest(Unknown Source)
    at org.w3c.www.protocol.http.HttpManager.runRequest(Unknown Source)
    at org.w3c.www.protocol.http.HttpURLConnection.connect(Unknown Source)
    at org.w3c.www.protocol.http.HttpURLConnection.a(Unknown Source)
    at org.w3c.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
    at java.net.URL.openStream(URL.java:1007)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:201)
    at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:263)
    at com.sap.engine.lib.xml.parser.Parser.parse_DTDValidation(Parser.java:282)
    at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:293)
    at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
    at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:146)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.loadDOMDocument(WSDLLoader.java:132)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:91)
    at com.sap.engine.services.webservices.espbase.wsdl.WSDLLoader.load(WSDLLoader.java:80)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.loadWSDLDefinitions(SAPServiceDelegate.java:201)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.initWSDL(SAPServiceDelegate.java:159)
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:113)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
    at javax.xml.ws.Service.<init>(Service.java:57)
    at com.verisign._2006._08.vipservice.VipSoapInterfaceService.<init>(VipSoapInterfaceService.java:41)
    at JEE_jsp_result_6740550_1225116575421_1225116585468._jspService(JEE_jsp_result_6740550_1225116575421_1225116585468.java:64)
    at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102)
    at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:433)
    at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240)
    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:309)
    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)
    09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:27:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@20ba3c
    09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:27:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:28:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@26e3bf
    09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:28:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:29:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@f827f6
    09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:29:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@a8646a
    09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:30:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:30:687 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=com.sap.engine.services.dbpool.cci.CommonConnectionHandle@c449f1
    09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out About to get connection from DS
    09:18:31:187 Info caf_gp_svcuser Thread[Timer-8,5,ApplicationThreadGroup] System.out DS connection=[email protected]
    09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ B E G I N ].timerId=15
    09:18:31:593 Info Administrator HTTP Worker [3] System.out SessionImpl::getContext():[ E N D ].timerId=[id:#15, elapsed: 0 ms.]

  • SAP Web services

    I am trying to use XCelsius 2008 to connect to SAP Webservices using Webservice Connector.
    I provided the WSDL URL and tried to Import. But got an error Unable to load URL.
    I am very new to Xcelsius and it seems like the SAP web service basic authentication is failing. Is there any way to hard code the username and password so that it will work?
    Or am i missing something important here? Any help would be appreciated.
    My email id is  [email protected]
    Thanks,
    Anil.

    Hello
    SAP Webservice refers to the develop of a WebService in Netweaver you can use ABAP or Java to do it.
    This link will be helpful
    [SAP Web Services - Definition and Tutorials/Weblogs|SAP Web Services - Definition and Tutorials/Weblogs]

Maybe you are looking for

  • Moving avergae price updation in material master for project stock

    Dear All, My query is pertaining to updation of MAP( moving average price) for project specific procurement ( as project stock) for valuated project stock. As  definelty the cost of procurement gets consumed by project .but i want to know does the pr

  • Oracle.jbo.AttrSetValException on extending an adf task flow in webcenter

    Hi, I have used EO validations and the validation messages are provided in the ResourceBundle.properties file.But whenever I deploy the adf task flow to webcenter spaces the messages are not shown and the following error occurs: <Jul 26, 2012 2:43:28

  • Flags and colors not taking (seems like a bug to me)

    I'm seeing a bit of an issue I am not sure I understand. I have a folder called "creative" with four albums in it: 1 2 3 4 If I select all the images in the folder and TAG them and add a ORANGE COLOR these tags and colors show up on all the images in

  • Web gallery problem

    Hi! I'm trying to upload a web gallery from one of my albums on iphoto. I've done this once before and it worked perfectly fine. Now though, everytime I press the web gallery button something pops up asking me to sign in to my .mac account. I say yes

  • Upgrade WLC 5508 to 7.4.121.0 problem

    After I upgraded WLC 5508 from 7.2.111.3 to 7.4.121.0, all 3602i APs don't associate with the controller.  All APs were working/associating with controller on 7.2.111.3 at same setting.  IP address of APs are setup as DHCP. The error message is "AP c