Problem in JAXM soap communication

Hello,
I'm sending simple message "some text here"
from soap client to server using JAXM
In the server i can access the message and show in the console
msg.writeTo(System.out);
How do i extract only the message from the soap envelop (How do i extract the message from the envelop in public SOAPMessage onMessage(SOAPMessage msg) method)?
This is my client
javax.xml.soap.Name name = envelope.createName("Text");
javax.xml.soap.SOAPBodyElement bodyElement = body.addBodyElement (name);
bodyElement.addTextNode ("Some Body text");
Thanks for your help

According to me, you should transform the result message to xml format, then use your favorite parser (e.g. SAX, DOM,...) to extract expected values.
                /* Do transform */
                TransformerFactory tFact = ransformerFactory.newInstance();
                Transformer transformer = tFact.newTransformer();
                Source src = msg.getSOAPPart().getContent();
                StringWriter sw = new StringWriter();
                StreamResult result = new StreamResult(sw);
                transformer.transform(src, result);
                DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                factory.setValidating(false);
                factory.setNamespaceAware(true);
                DocumentBuilder parser = factory.newDocumentBuilder();
                InputSource inSource = new InputSource(new ByteArrayInputStream(sw.toString().getBytes()));
                Document dom = parser.parse(inSource);
                /* xml processing goes here. At this time, you have a DOM tree in the memory, write code to get values */
                .........hope this helps

Similar Messages

  • Getting error in target SOAP communication channel

    Hi all,
    I am trying to send data from Http client to Webservice.In moni i got a message processed successfully means getting black flag.But i got an error in SOAP Communication channel as "error in response".
    I got this message from that error 
    <b>"SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 407 Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied.  )"</b>
    Source side i dont configure Http adapter.Target side i configured SOAP adapter.In that SOAP adapter i configured these fields.1)Target URL 2)Configure Proxy 3)Configure proxy user authentication.
    I want get response from webservice.Please help me.
    Thanks,
    Gopi.

    Hi,
    Make sure that you have specified the proper host and port values, in the text box that appears when you check the configure proxy check box(in receiver soap adapter).
    Looks like the webservice requires a proxy authentication.
    Select the check box "configure proxy user authentication"(in receiver soap adapter) and provide the correct username and password.
    Regards,
    Smitha.
    Message was edited by: Smitha Rao

  • Problem in creating new communication channel template in IR

    Hi experts,
    I currently have problems with creating new communication channel template in Integration Repository. If I choose the New-Context (Adapter Objects-->Communication Channel Template) the dialog "CREATE OBJECT" is shown. After I have inserted the Name of my template I push the create button.
    Then the following error occurs:
    STOP: Internal error: Object cannot be changed in display mode
    DETAILS: Internal error: Object cannot be changed in display mode(CANT_SET_MODIFIED).
    So can anybody help me. Thanks for your help.
    Best regards.
    Mario

    Hi Mario,
                This is genral problem appearing in PI 7.0 with SP12.
                Previously, i have the same problem.
                i.e STOP: Internal error: Object cannot be changed in display mode
    DETAILS: Internal error: Object cannot be changed in display mode(CANT_SET_MODIFIED)
                Regarding this we raise an OSS note SAP people.
                they gave the suggestion that update with SP13.
              i discuss with basis team and install the SP13.
               now the problem is solved, i can able to create the Communication Channel Template.
    Please award points, if it really help to u
    Regards
    Mahesh.

  • Problems with MSA - IPC communication

    Hello.
    We experience some problems with MSA -> IPC communication on our Mobile Clients.
    The version of CRM is 7.0.
    The problem seems to be related to mobile clients switching status (online | offline | vpn connected | disconnected | etc).
    It is difficult to predict the behaviour of a general salesperson, but regardless when the mobile client is awaken and MSA is already running, the connection to the IPC should work, right ?
    I wonder if anyone else has experienced any problems related to this ?
    Our platform is Windows 7, we use Checkpoint vpn-client.
    From what i've seen during testing, the problem is not consistent, it arises at odd times but it seems to be related to Network/VPN connection.
    What we have done is edit the tomcat\conf\server.xml file to bind tomcat to localhost address: 127.0.0.1. I've not been able to reproduce the problem when binding tomcat to this address. However, i would really appreciate any feedback on this matter.
    BR Gerhard.

    Does the user has Admin rights for the laptop ?
    Rgds,
    Shobhit

  • HOW TO CREATE SERVICE FOR SENDER SOAP COMMUNICATION CHANNEL FOR ECC PROXY

    Hi Experts,
    I need generate the service for sender soap communication channel for target url to receive the  inbound proxy.
    my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method .
    i am using SOAP sender and SOAp receiver communication channel .i need to provide the target url for this communication channel.
    how to generate the url for this and what is the transaction code .
    Please help us.
    Regards
    Ravinder.S

    Hi Ravinder,
    Q.my scenario is like SOAP to proxy. while using  receiver proxy also we are planing using AAE method.
    SOAP to Poxy in this case.
    For sender  SOAP system, we can generate the WSDL link in ID part.
    for Reveiver proxy give the integration engine URL.
    http://IP:PORT/sap/xi/engine?type=entry
    how to generate the url for this and what is the transaction code
    There is no transaction code for generating the URL.
    i hope this will help.
    Regards,
    Kesava.

  • Receiver SOAP Communication channel -- Target URL

    Hi Experts,
    Can anyone provide some inputs for my below question?
    How the receiver SOAP Communication channel internally calls the Target URL?
    What is the internal process behind this call?
    I would really appreciate you all if could provide answers.
    Thanks & Regards,
    Prabu Muthu

    Hi...
    To be able to send SOAP messages from the Integration Server/PCK to remote clients or Web service servers, you must first configure the receiver SOAP adapter. The receiver adapter supports system acknowledgments but not application acknowledgments
    Find the below link .
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
    Regards,
    Leela

  • SOAP communication channel

    Hi,
    I am configuring sender SOAP communication channel. I see only "CENTRAL ADAPTER ENGINE" in the Adapter engine type. I do not see any INTEGRATION SERVER  in the drop down option.
    Kindly help.

    Hi,
    Why do you need INTEGRATION SERVER in the drop down option??
    you have to select the Adapter Engine, Transport Protocol and Message Protocol.
    In the Adapter Engine you need to select the CENTRAL ADAPTER ENGINE . This is since you have only one adapter engine. If there is any local AE, and it is correctly installed, then it will also appear in the drop down.
    But INTEGRATION SERVER, which you are askin never appears!!
    Please explain if u need further clarifications.
    Cheers,
    Souvik

  • Can JAXM replace AXIS for SOAP communication?

    Hi,
    I am new to Java and SOAP. I've been asked to rewrite some java code that accesses a soap service at a sister company. Currently the code uses apache axis & saaj (so there are about 7 jars included) to do the communication with soap. I've been asked to trim this code down to a much lighter weight program (and I quote... 1 jar if possible). Can JAXM do this, or does anyone else have a suggestion as to other libraries out there that can help interface with soap using less overhead?
    Thanks,
    mrazz

    Hello,
    My interface is SOAP to SOAP..which has 2 operations..1.check..2.update.
    If your receiver determination is set to Operation Specific, then you may have not placed any specific receiver for your update operation. Also check the namespaces that is declared in your receiver determination.
    Hope this helps,
    Mark

  • Monitoring problem in async SOAP receiver adapter

    Hi!
    I have a File to SOAP asynchronous scenario.
    I want to see in monitoring (sxi_monitor) if problem occured when calling the webservice, for example when the connection is refused, or a timeout.
    In Runtime Workbrench, I can see the errors in Communication Channel Monitoring and in Message Monitoring from Component Adapter Engine.
    I have configured an alert rule for receiving alerts when an error occured, but <u>I don't receive any alert</u>. And when I go to the transaction SXI_MONITOR in my system XI, the status of the message is <u>"Processed successfully" instead of "System Error"</u>.
    Any idee of how to solve this?
    Thanks in advance,
    Laurence

    Hi,
    In this link you will find the list of the container elements.
    Declare these container elements in your Alert Category, and use them between & CONATINERELEMENT& in your alert text and these will be filled up in the run time.
    the link to your message will be added by default in the Post Processing Steps. You need not do anything special for this.
    http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
    Regards
    Bhavesh

  • JAXM - SOAP Faults

    Hi,
    I have an almost working JAXM standalone client. However i have one problem, i cant seem to get SOAP Faults back from the SOAP Server (MS SOAP), instead i get a java exception as shown below. All other calls work fine, i would like to be able to retrieve the error information from the fault.
    I am using the JAXM version that comes with the JWSDP.
    I am wondering if anyone has JAXM working with SOAP faults?.. i dont want to have to change my implementation.
    Kris
    java.io.FileNotFoundException: http://TAZ//MeridioSOAP//MeridioSOAP.asp
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:549)
         at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
    javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:288)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)

    It seems no one has ever had a SOAP fault and cant answer my question. Anyway more information. I have tracked the problem down to the following :
    As per the SOAP Specification, a normal SOAP response returns with the HTTP Post code 200 OK, and a fault returns with the HTTP Post code 500 Internal Server Error.
    The class sun.net.www.protocol.http.HttpURLConnection seems to throw an exception if the code returned isnt 200. Obvously this isnt any good for SOAP faults. Any ideas as to ways around this?
    btw, i changed the version of the JDK i was using from 1.3.0 to 1.3.1_02 and the exception message changes from what i stated in my first message to the following which makes a bit more sense.
    java.io.IOException: Server returned HTTP response code: 500 for URL: http://TAZ//MeridioSOAP//MeridioSOAP.asp
         at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:562)
         at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
         at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:166)
         at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
    java.lang.NullPointerException
         at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:657)

  • Help me pls to resolve the problem: WebService client SOAP exception: SAXException: Could not instantiate bean ...

    Hi all,
    I use Weblogic 6.1 SOAP
    If any body know what does this mean and how this may be resolved please
    help me
    I try to send JavaBean class "A" which includes an array of JavaBean class
    "B" which includes an array of string objects
    from server side to the client.
    class A {
    B[] aBeans
    setABeans(B[] aBeans) {}
    getABeans() {}
    class B {
    String[] props;
    setProps(String[] props) {}
    getProps() {}
    And only half of the method invocation is ok - data is transmitted by soap
    and is displayed
    at the client side in "verbose=true" mode and i see that data is received
    completely but the client side JavaBean class "A"
    was not initialized because the exception was thrown when soap trying to
    instantiate JavaBean class "B":
    SAXException: Could not instantiate bean: B
    I looked at jdk API and the InstantiationException is thrown only if class
    is an interface or an abstract class,
    but class "B" is not abstract or interface, it is simple JavaBean class.
    What is the trouble?
    Help me pls

    Hi, Pieter!
    Thanks in advance, this solve a problem.
    "Pieter Degraeuwe" <[email protected]> wrote in message
    news:3be00299$[email protected]..
    >
    Hi!
    I think I know the problem.
    Does your JavaBean has a default constructor (a parameterlessconstructor).
    >
    Try it!
    greetings
    Pieter
    "Michael T" <[email protected]> wrote:
    Hi all,
    I use Weblogic 6.1 SOAP
    If any body know what does this mean and how this may be resolved please
    help me
    I try to send JavaBean class "A" which includes an array of JavaBean
    class
    "B" which includes an array of string objects
    from server side to the client.
    class A {
    B[] aBeans
    setABeans(B[] aBeans) {}
    getABeans() {}
    class B {
    String[] props;
    setProps(String[] props) {}
    getProps() {}
    And only half of the method invocation is ok - data is transmitted by
    soap
    and is displayed
    at the client side in "verbose=true" mode and i see that data is received
    completely but the client side JavaBean class "A"
    was not initialized because the exception was thrown when soap trying
    to
    instantiate JavaBean class "B":
    SAXException: Could not instantiate bean: B
    I looked at jdk API and the InstantiationException is thrown only if
    class
    is an interface or an abstract class,
    but class "B" is not abstract or interface, it is simple JavaBean class.
    What is the trouble?
    Help me pls

  • Problems in IDOC receiver communication channel

    Hi,
    I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
    Please assist.
    Rgds
    Kishore

    OK in that case, we are getting the following error in the Message monitoring:
    <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
      <SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
      <SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
      <SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
    Please check and assist.
    Rgds
    Kishore

  • Problem in File Sender Communication channel

    Dear all,
    We have FIle TO RFC scenario, which have been running in Production since long time.
    Problem :  Many of the time we have obsereved that even if the FTP is up and running , but file is not getting picked from ftp server. File name and all other details are maintained correctly. Can you please suugest me to resolve this issue.
    Regards,
    Raghvendra

    First of all: the connect parameter should be set to 'Per Transfer': this ensures that a new connection to the FTP server is established for each file transfer. That means that you don't loose connection to the FTP server in case of a hick-up.
    Second: are there any errors in your communication channel monitoring?

  • Problem Proxy to SOAP Synchronous

    Hi Experts, I was looking for a solution to this problem, but I could not find the solution, I hope you can help me.
    I have the scenario PROXY ==> PI ==> SOAP (Synchronus).
    When the Web Service is ok, I have no problems, my problem is with the Fault Exception, because I tested it in SoapUI, and I'm getting this message.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.GeneratedMethodAccessor267" line="unknown" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>
    So, I was reading a lot of threads, those said to copy the structure, but it doest not work.
    I tried to check the "Do Not Use SOAP Envolve", but when I did that I got this error.
    Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 415 Unsupported Media Type
    When I unchecked I got this error.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~</SAP:P1>
      <SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
      <SAP:P3>on: Cannot create target element /ns0:Fault. Value</SAP:P3>
      <SAP:P4>s missing in queue context. Target XSD requires a~</SAP:P4>
      <SAP:AdditionalText />
      <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_RecursosHumanos_ServicioEmplead~; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:Fault. Values missing in queue context. Target XSD requires a~</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    I could never see the Fault Structure in PI and neither in Web Service Navigator.
    Please, I need some help.
    Thank you very much.
    Regards

    If I test it in Soap UI I get the Fault, and in WsNavigator I can see the FaultCode and FaultString as a message on the top of the page.
    I do not know what more to do.
    <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
       <S:Body>
          <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
             <faultcode>S:Server</faultcode>
             <faultstring>Error al insertar Domicilio en servicio Empleado</faultstring>
             <detail>
                <FaultException:FaultException xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.interacciones.com.mx/ServicioEmpleado/" xmlns:FaultException="http://www.interacciones.com.mx/ServicioEmpleado/"/>
                <ns2:exception class="mx.com.interacciones.servicioEmpleado.FaultException_Exception" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
                   <message>Error al insertar Domicilio en servicio Empleado</message>
                   <ns2:stackTrace>
                      <ns2:frame class="mx.com.interacciones.servicioEmpleado.ServicioEmpleadoImpl" file="ServicioEmpleadoImpl.java" line="87" method="agregarEmpleado"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="native" method="invoke0"/>
                      <ns2:frame class="sun.reflect.NativeMethodAccessorImpl" file="NativeMethodAccessorImpl.java" line="39" method="invoke"/>
                      <ns2:frame class="sun.reflect.DelegatingMethodAccessorImpl" file="DelegatingMethodAccessorImpl.java" line="25" method="invoke"/>
                      <ns2:frame class="java.lang.reflect.Method" file="Method.java" line="597" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="101" method="invoke"/>
                      <ns2:frame class="weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker" file="WLSInstanceResolver.java" line="83" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.InvokerTube$2" file="InvokerTube.java" line="152" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="264" method="invoke"/>
                      <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="604" method="__doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="563" method="_doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="548" method="doRun"/>
                      <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="445" method="runSync"/>
                      <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="275" method="process"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="454" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="250" method="handle"/>
                      <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="140" method="handle"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="319" method="run"/>
                      <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="232" method="post"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="310" method="doPost"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service"/>
                      <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="87" method="service"/>
                      <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run"/>
                      <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3594" method="run"/>
                      <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs"/>
                      <ns2:frame class="weblogic.security.service.SecurityManager" file="SecurityManager.java" line="121" method="runAs"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2202" method="securedExecute"/>
                      <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2108" method="execute"/>
                      <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1432" method="run"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute"/>
                      <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run"/>
                   </ns2:stackTrace>
                </ns2:exception>
             </detail>
          </S:Fault>
       </S:Body>
    </S:Envelope>

  • Problem Consuming webservice -- SOAP UI

    Hello Gurus,
    We have generated a web service from SAP and trying to consume the web service from SOAP UI (external tool), but the SOAP UI tool is generating some error as mentioned below.
    Exception_Name> CX_ST_MATCH_ELEMENT
    Exception_Text> System expected end of element 'GetQueryViewData': Main Program:/1BCDWB/WSS0051118152402496573| Program:/1BCDWB/WSS0051118152402496573| Line: 58| Valid:X
    Note: I have tested the web service from the WS Navigator and I am able to get the response (all Ok).
    Kindly let me how I can fix the issue, I belief the problem is XML transformation related (XSLT_TOOL).
    Regards,
    Abhi.

    Hi Abhi,
    seems that in SOAPUI, you need to pass the correct data (exact length of SAP Fields). Also try by removing "?" symbols whereever not necessary to pass data(optional values).
    Hope this may help you...
    Cheers,
    Kris

Maybe you are looking for