Problem in SOAP Request

Hi Experts,
I am working on SOAP-XI-Proxy Scenario. The Java system is using the WSDL from XI and triggering the following request
  <?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <SearchCustomer xmlns="urn:com.axonglobal.sbc.icase.customersearch">
  <BPNo />
  <Surname>Jones</Surname>
  <FirstName />
  <Phone />
  <Email />
  <PostCode />
  <HouseNo />
  <FlatNo />
  <Street />
  <Building />
  <Estate />
  </SearchCustomer>
  </soapenv:Body>
  </soapenv:Envelope>
But it receives the following error.
<?xml version="1.0" encoding="utf-8" ?>
- <!--
see the documentation
  -->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
- <SOAP:Body>
- <SOAP:Fault>
  <faultcode>SOAP:Server</faultcode>
  <faultstring>Server Error</faultstring>
- <detail>
- <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
  <context>XIAdapter</context>
  <code>MalformedMessageException</code>
- <text>
- <![CDATA[
Unexpected content in SOAP:Body; nested exception caused by:
com.sap.aii.messaging.util.XMLScanException: Unexpected content in SOAP:Body
     at com.sap.aii.messaging.mo.Message.reparseRootDocument(Message.java:1014)
     at com.sap.aii.messaging.net.MIMEInputSource.readSOAPPart(MIMEInputSource.java:619)
     at com.sap.aii.messaging.net.MIMEInputSource.decodePart(MIMEInputSource.java:611)
     at com.sap.aii.messaging.net.MIMEInputSource.readBody(MIMEInputSource.java:379)
u2026.
u2026u2026.         
  ]]>
  </text>
  </s:SystemError>
  </detail>
  </SOAP:Fault>
  </SOAP:Body>
  </SOAP:Envelope>
IMP:- The call is not registered in the Message Monitoring at Adapetr Level or at Integration Engine Level, as I believe it is rejected as the Message Format is not correct .
Is it because , the  request message is wrapped with the SOAP Envelope with the notation u2018<soapenv:Envelopeu2019 instead of the traditional u2018<SOAP:Envelopeu2019 notation?
We tested the same with XML Spy and it is working fine with the same payload.
Pls advise.
Regds.
Edited by: Subhendu Sahu on Apr 24, 2009 12:39 PM

Hi,
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <SearchCustomer xmlns="urn:com.axonglobal.sbc.icase.customersearch">
<BPNo />
<Surname>Jones</Surname>
<FirstName />
<Phone />
<Email />
<PostCode />
<HouseNo />
<FlatNo />
<Street />
<Building />
<Estate />
</SearchCustomer>
</soapenv:Body>
</soapenv:Envelope>
Use the below format:
<?xml version="1.0" encoding="UTF-8" ?>
   <SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'>
     <SOAP:Body>
        <SearchCustomer xmlns="urn:com.axonglobal.sbc.icase.customersearch">
          <BPNo />
          <Surname>Jones</Surname>
          <FirstName />
          <Phone />
          <Email />
          <PostCode />
          <HouseNo />
          <FlatNo />
          <Street />
          <Building />
          <Estate />
        </SearchCustomer>
     </SOAP:Body>
</SOAP:Envelope>
Hopefully it will work with the above given format...if not then remove the namespace associated with SearchCustomer and test.
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
- <soapenv:Body>
- <SearchCustomer xmlns="urn:com.axonglobal.sbc.icase.customersearch">
Are you testing with sign in the payload??....if yes remove it.
Regards,
Abhishek.
Edited by: abhishek salvi on Apr 24, 2009 7:57 PM

Similar Messages

  • Problem with WebLogic 10.1 and SOAP request

    I have some relatively simple code that is making a SOAP request and trying to parse the response. The code works fine in Tomcat 6, but fails when running under WebLogic 10.1. At first, the problem was with the implementations of MessageFactory and SOAPConnectionFactory. After some research, I added the following to the startWebLogic.sh file
    -Djavax.xml.soap.MessageFactory=com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl
    -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConnectionFactoryImpl
    That resolved the initial problems, but now I get the following error when making a call to the getTextContent() method of an instantiation of the org.w3c.dom.Node class.
    java.lang.AssertionError: UNIMPLEMENTED
         at weblogic.xml.domimpl.NodeImpl.getTextContent(NodeImpl.java:198)
    In my research, it seems that the "-Djavax.xml.soap.MessageFactory=com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl " option should have resolved that issue, but it does not. I am including the relevant section of code below for reference. If anyone has a suggestion as to how to fix this issue, I would be very grateful. Thanks in advance!
         fis = new FileInputStream(_outputFileName);
         MimeHeaders hd = new MimeHeaders();
         hd.addHeader("Content-Type", "text/xml;charset=UTF-8");
         hd.addHeader("SOAPAction", "/service/doCallAPI");
         MessageFactory factory = MessageFactory.newInstance();
         SOAPMessage request = factory.createMessage(hd, fis);
         SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
         SOAPConnection connection = soapConnectionFactory.createConnection();
         SOAPMessage response = connection.call(request, new URL(_pdfHostUrl));
         NodeList documents = response.getSOAPBody().getElementsByTagName("FileProp");
         Node node = documents.item(0);
         String textContent = node.getTextContent();
    -----------------------------------------------------------------

    Hi Else,
    We'd really like to reproduce this problem and get to the bottom of what is causing it, so that you could upgrade in the future.  Would you be willing to send me a data set consisting of your TDM, TDX, TDV, and video file?  You can either post here or send it directly to my email at:
    [email protected]
    Thanks,
    Brad Turpin
    DIAdem Product Support Engineer
    National Instruments

  • Soap request with attachment --problem in deploye to jboss useing Jdevelope

    using Jdeveloper and oc4j application server i made two application.
    In application one i exposed a web service method.In this application their is a handler class which able to handle soap request and response with attachment.
    In application two a client is sends a soap request with attachment.
    If i deploye it in oc4j it is working fine. But if i Deploye to JBoss server [i made a jboss application server connection] and then trying to send the soap request with attachment from the client application i gets the following errors--
    Exception in thread "main" javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:152)
         at etrans.TripBean.a.ClientGateWay.msgEnvelope(ClientGateWay.java:50)
         at etrans.TripBean.a.ClientGateWay.main(ClientGateWay.java:60)
    Caused by: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Connection refused
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:148)
         ... 2 more
    Caused by: javax.xml.soap.SOAPException: Message send failed: Connection refused
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:458)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:865)
         ... 4 more
    Caused by: java.net.ConnectException: Connection refused
         at java.net.PlainSocketImpl.socketConnect(Native Method)
         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
         at java.net.Socket.connect(Socket.java:516)
         at java.net.Socket.connect(Socket.java:466)
         at java.net.Socket.<init>(Socket.java:366)
         at java.net.Socket.<init>(Socket.java:208)
         at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:202)
         at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3115)
         at HTTPClient.HTTPConnection.doConnect(HTTPConnection.java:3858)
         at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:2921)
         at HTTPClient.HttpOutputStream.close(HttpOutputStream.java:421)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.sendMessage(HttpSOAPConnection.java:724)
         at oracle.j2ee.ws.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:373)
         ... 5 more
    Am i made any mistake to deploye to jboss or it is not possiable to access the web service in such way?
    please suggest me what is the procedure to recover from this.

    Hello,
    How do you package you WS client application to be deployed in JBoss?
    The JAX-RPC clients are not that portable you may need to recompile the client with JBoss WebService implementation/tools, and check that you do have the different deployment descriptors for the client too.
    Regards
    Tugdual Grall

  • Error with SOAP Request to calendar web service

    Hi
    I'm sending the following SOAP request to a calendar web service to create an appointment in the calendar. The response returns what seems to be a syntax error ("The Create method did not have a proper element in the request") but I can't see the cause of the fault. Any suggestions on what it may be? It's an 11g DB.
    Many thanks
    -x-POST-x-
    POST /ocws-bin/ocas.fcgi HTTP/1.0
    Content-Type: text/xml; charset="utf-8"
    Content-Length: 993
    SOAPAction: SOAPAction: "http://www.oracle.com/WebServices/Calendaring/1.0/Create"
    Connection: close
    <SOAP-ENV:Envelope
    xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header><auth:BasicAuth xmlns:auth="http://soap-authentication.org/2002/01/">
    <Name>CalendarName</Name><Password>CalendarPassword</Password>
    </auth:BasicAuth> </SOAP-ENV:Header>
    <SOAP-ENV:Body><cwsl:Create xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/"><CmdId>ITS APPOINTMENT</CmdId><iCalendar>
    <vcalendar prodid="-//Oracle//Calendaring//Calendarlet//EN" version="2.0">
    <vevent><class>PUBLIC</class>
    <description>Calendar Body</description>
    <dtstart value="DATE-TIME">20102905T120000</dtstart>
    <duration>P00DT0H30M00S</duration>
    <location>Location of user</location>
    <summary>Incident ID - (name of user])</summary>
    <uid>XGjRVnpReQALNsILlBlvcyXGCoUyXF</uid>
    <x-oracle-eventtype>APPOINTMENT</x-oracle-eventtype>
    <priority>5</priority>
    </vevent>
    </vcalendar>
    </iCalendar></cwsl:Create></SOAP-ENV:Body></SOAP-ENV:Envelope>
    -x-RESPONSE-x-
    HTTP/1.1 500 Internal Server Error
    Date: Thu, 27 May 2010 08:22:16 GMT
    Server: Apache/2.2.4 (Unix) mod_ssl/2.2.4 OpenSSL/0.9.7a mod_fastcgi/2.4.6
    OCAS-ProcTime: 407
    Connection: close
    Content-Type: text/xml; charset=utf-8
    <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
    <soap:Body>
    <soap:Fault>
    <faultcode>soap:Server.Error::System::SOAPRequest</faultcode>
    <faultstring>The Create method did not have a proper element in the request</faultstring>
    <detail>
    <cwsl:Error xmlns:cwsl="http://www.oracle.com/WebServices/Calendaring/1.0/">
    <Class>Error::System::SOAPRequest</Class>
    <Code>0020-00-00-00000034</Code>
    <Line>3180</Line>
    <FileName>SOAPRequestHandler.cpp,v</FileName>
    <Version>1.57</Version>
    <LastMod>2007/05/30 21:13:25</LastMod>
    <Author>pscattol</Author>
    <Date>Thu May 27 09:22:16 2010</Date>
    <PID>26152</PID>
    <TID>3044838304</TID>
    <Level>Error</Level>
    </cwsl:Error>
    </detail>
    </soap:Fault>
    </soap:Body>
    </soap:Envelope>

    Hi,
    I am having problem using dii client, while sending a
    request to c# webservice. error follows
    QName QNAME_TYPE_STRING = new QName(NS_XSD,
    "string");
    call.setReturnType(QNAME_TYPE_STRING);
    call.setOperationName(new QName(BODY_NAMESPACE_VALUE,
    "GetDetails"));
    call.addParameter("String_1", QNAME_TYPE_STRING,
    ParameterMode.IN);Do you need another call to addParameter here?
    String[] params = { "02", "2004" };
    String result = (String)call.invoke(params);

  • Sending SOAP request from XI and writing a scheduler for this

    Dear XI Experts,
    My scenario is as follows.
    We have two landscapes
    1)     XI, R/3
    2)     Client System(Remote, Other than SAP)
    Now we have to pull the data from client system using WSDL (There will be one method for pulling the data in the WSDL file). The WSDL is provided by the client. We are importing that WSDL as external definition in Integration Repository and implementing the scenario “SOAP to XI to RFC” and configuring it Integration Directory.
    Remember the client will not send the data to XI. Only we have to pull the data as mentioned above.
    Problems:-
    (i)     How to send SOAP request to the client using XI only?
    (ii)     How to write a scheduler for this?
    please help us.
    Thanks...
    Praveen Gujjeti

    Ur Suggestion
    "My proposition looks like that. in R/3 you have scheduled RFC call in some program. This RFC calls XI and XI is calling using SOAP adapter your client. Then response go back to your RFC and you can handle this data."
    As you mentioned, I am not scheduling any RFC call in R/3. If you go through my first query u can find two points where I am having some doubts......
    How to send SOAP request to the client using XI only? Is it possible to send a SOAP request from XI?
    If so,
    (ii) How to write a scheduler for this? So that it will invoke the webservice and get the data from client application(system)

  • How to test SOAP request using XML SPY

    Hi,
    1. I am new to WebServices concept, I have downloaded the wsdl file and now I need to test the SOAP requests using XML Spy. However, when I try to test the SOAP request generated by XML Spy I receive an error "Internal Error: Session is not available. Aborting" , How do I go ahead to generate the session, Is there a way I can provide the Username and password in the XML Spy to generate something like session.
    2. The second problem that I am facing is when I import the WSDL in XML Spy and generate the SOAP request, for all the fields xml tags gets populated with "aaaaaaaaaaaa" kind of data through out. Am i doing something wrong ? Is there some step while creating a SOAP request that I am missing becasue of which the gibbrish data is being populated as default ?
    Please Help !
    Thanks .

    I got my SOAP Requests tested using SOAP UI .. However I am still looking for ways to test it using XML SPY.
    In the SOAP UI Tool just do right click and select Add WS Security Token ..
    Thanks :)

  • SOAP- XI- RFC , while posting soap request thru SPY , getting exception,

    Hello friends,
    I am trying <b>SOAP->XI->RFC</b> scenario. would like to explain in brief about requirement then <b>let me know if this is correct approach</b>
    <i>Our client wants a pull approach from R/3 , for example lets say he wants to get Material Master data from R/3.
    So he will send a SOAP request with the material number and r/3 should return back the details.</i>
    <b>So we have decided to go with SOAP->XI->RFC approach
    That means a sender SOAP Adapter and a receiver RFC adapter,</b>
    I have done all the designing, like creating my own DataType,MessagType all interfaces etc.
    then i created a Bussiness system of type third party with host name as XI host name to use for sender, and a business system of type Web As ABAP and used one of the R/3 as receiver system.
    Doubts: Once i created Soap channel in my sender businees system(where Interface name i gave my Message Interface name and its Namespace), and the receiver channel in my another bussiness system, i created the entire scenario using Configuration Wizard.
    NOW THE PROBLEM STARTS.
    After clicking Define Web Service , it asks for URL
    i gave following url
    http://ps3181:50000/XISOAPAdapter/MessageServlet?channel=TPBS_Rohit:soapChannel
    TPBS_Rohit is my Sender (third party bussiness system name), and soapChannel is the channel under it.
    <b>tell me if this is right</b>
    Then in the Message Interface i selected my Message Interface name that i had created in Design for publishing.
    <u><b>MAJOR DOUBT</b></u>
    <b>It Asks for
    Service :
    Interface Name :
    Interface NameSpace :
    what do i give here.</b>
    this is what i have given
    Service : TPBS_Rohit, Sender (third party bussiness system name)
    Interface Name : MI_SOAP <again the same message interface name that i have published earlier>
    Interface NameSpace : same namespace.
    AM i right ???
    I am sure somthing is wrong since when i tried sending a SOAP request using XML SPY , this is what i get.
    [code]<?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Body>
              <SOAP:Fault>
                   <faultcode>SOAP:Server</faultcode>
                   <faultstring>Server Error</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>Exception</code>
                             <text><![CDATA[
    java.lang.Exception: invalid channel (party:service:channel) = TPBS_Rohit:soapChannel
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:498)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
              ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>[/code]
    Please Let me know where have i gone wrong ?

    hi manikandan,friends
    i changed the url to http://ps3181:50000/XISOAPAdapter/MessageServlet?channel=:TPBS_Rohit:soapChannel
    colon included.
    but now i get the following error trace in SPY ..
    [code]<?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Body>
              <SOAP:Fault>
                   <faultcode>SOAP:Server</faultcode>
                   <faultstring>failed to call the adapter engine</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>DeliveryException</code>
                             <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:697)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:221)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:543)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.aii.messaging.srt.BubbleException: failed to call the adapter engine [null "null"]; nested exception caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
         at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:122)
         at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)
         at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:576)
         ... 20 more
    Caused by: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:NO_RECEIVER_CASE_BE:
         at com.sap.aii.adapter.xi.ms.XIEventHandler.onTransmit(XIEventHandler.java:366)
         at com.sap.aii.af.ra.ms.impl.core.queue.CallConsumer.onMessage(CallConsumer.java:123)
         at com.sap.aii.af.ra.ms.impl.core.queue.Queue.run(Queue.java:419)
         at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
         at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)
         at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)
              ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>[/code]

  • Problem with soap receiver adapter

    Hi All
    I have Idoc sender and soap receiver in my scenario.
    I am calling web service deployed on WAS.
    The web service is getting called but the acknowledgement message in xi contains following system error acknowledgement because of which xi changes the status of message to WAIT and starts retrying.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapterFramework</SAP:Category>
      <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.MessagingException: java.net.SocketTimeoutException: Read timed out: com.sap.aii.af.ra.ms.api.RecoverableException: java.net.SocketTimeoutException: Read timed out</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack />
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please anybody can help to resolve this problem. This scenario has worked without any error previously.
    Thanks in advance
    Beena

    Hi Bhavesh,
    It is an Async call where method does not return anything.
    I added entries in IDX_NOALE but still it is setting the message status to WAIT and does retry.
    Following is the Audit Log in Runtime workbench :
    Audit Log for Message: 22b3052d-c519-034e-85db-e65d541d6414
    Time Stamp Status Description
    2006-12-13 10:25:23 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:25:23 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:25:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:25:24 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:30:24 GMT+05:30 2006.
    2006-12-13 10:25:24 Success The message status set to WAIT.
    2006-12-13 10:30:25 Success Retrying to deliver message to the application. Retry: 1
    2006-12-13 10:30:25 Success The message was successfully retrieved from the receive queue.
    2006-12-13 10:30:25 Success The message status set to DLNG.
    2006-12-13 10:30:25 Success Delivering to channel: INSPWCCT_PVtoSAP_Ack
    2006-12-13 10:30:25 Success SOAP: request message entering the adapter
    2006-12-13 10:35:28 Success SOAP: call failed
    2006-12-13 10:35:28 Success SOAP: sending a delivery error ack ...
    2006-12-13 10:35:28 Success SOAP: sent a delivery error ack
    2006-12-13 10:35:28 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2006-12-13 10:35:28 Error Exception caught by adapter framework: Read timed out
    2006-12-13 10:35:28 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2006-12-13 10:35:28 Success The asynchronous message was successfully scheduled to be delivered at Wed Dec 13 10:40:28 GMT+05:30 2006.
    2006-12-13 10:35:28 Success The message status set to WAIT.
    I have tried this scenario earlier. I am sending the same Idoc from R3 which was processed successfully earlier.
    Thanks
    Beena.

  • There is no payload in Soap request

    Hi Expert,
    I am testing Soap to RFC scenario. I am firing the soap request using Altova xmlspy. I am getting the response as cannot read payload. I checked in the Moni, no payload is coming to xi. but i am sending data through soap request. Below the response wat i am getting
    <?xml version="1.0"?>
    <!-- see the documentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
         <SOAP:Body>
              <SOAP:Fault>
                   <faultcode>SOAP:Server</faultcode>
                   <faultstring>Server Error</faultstring>
                   <detail>
                        <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
                             <context>XIAdapter</context>
                             <code>RecoverableException</code>
                             <text><![CDATA[
    com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.DeliveryException: XIServer:CANNOT_READ_PAYLOAD:
         at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:919)
         at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process(ModuleLocalLocalObjectImpl3.java:103)
         at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:258)
         at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process(ModuleProcessorLocalLocalObjectImpl0.java:103)
         at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:167)
         at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:424)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         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)
              ]]></text>
                        </s:SystemError>
                   </detail>
              </SOAP:Fault>
         </SOAP:Body>
    </SOAP:Envelope>
    Please help me out in this issue
    Thanks,
    Venky

    Hi,
    Check whether your payload message which you are passing in HTTP Client tool is correct or not, try to copy the payload from Integration Repository while testing your mapping program.
    Also check the Integration Engine Configuration runtime parameters,
    Open Transaction SXMB_ADM -> Integration Engine Configuration -> Change Specific Configuration
    Check the values of below given parameters for runtime category, these values must be maintained:
    LOGGING, LOGGING_SYNC, LOGGING_PROPAGATION, TRACE_LEVEL and TRACE_LEVEL_PROPAGATION.
    Look into this thread ... it seems something similar with your problem.
    Payload of SOAP-Message cannot be read Try these solutions.
    Regards
    Aashish Sinha

  • Web Service Call From Proxy Client in ABAP: View SOAP Request

    Hello All,
    We are working on a scenario where we have to connect to a web service from ABAP. We have extracted the WSDL, and generated the client proxy, and configured a Logical Port. However, at the time of actual call, we receive an error message "Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message.". We suspect that this is a problem with the SOAP Header, which might be missing some tags, which are required by the Web Service. Problem is, we can not trace the Web Service SOAP Header. We can not see it in SOAMANAGER, or any other transaction as such. Does any body have an idea where to look for the complete SOAP Request, in case of a Client Proxy call?
    Thanks and Regards,
    Sid

    Hello Sebastian,
    Thanks for replying. We are using a higher support pack level, and hence we do not use LPCONFIG; rather we use SOAMANAGER to manage the web service logical ports. Further, SMICM would display us ICM Logs, where as we need the exact SOAP request that has been generated. We tried ST11 with no luck.
    Finally, I feel this is a wrong forum to ask such an application related question. I will close this thread and open a new thread in either PI or ABAP Forum.
    Thanks and Regards,
    Sid

  • Problems with SOAP Adapter/Interface

    Hi Experts,
    we currently try and experiment with XI 3.0 Stack 09 and the SOAP adapter respectively.
    We started with a simple interface (foo..., see wsdl attachment) that we want to provide by XI.
    All configurations (SLD, Integration Repository, Integration Directory) should have been done accordingly as we suppose, similar to other szenarios we have already implemented.
    When we send a SOAP request based on a generated wsdl to XI we get the exception at the bottom of this text, containing e.g.
    com.sap.aii.messaging.srt.BubbleException: error during conversion [null "null"];
    com.sap.aii.messaging.util.XMLScanException: Parsing an empty source. Root element expected!
    For sending the SOAP message we used XMLSpy.
    Did someone have similar problems or can give us an working WSDL example, or some hint?
    Thanks in advance,
    Klaus Lukas
    foo.wsdl
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com" name="foo_out_sync">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn://poreceive.xi.pse.siemens.com" targetNamespace="urn://poreceive.xi.pse.siemens.com">
                   <xsd:element name="foo" type="foo_DT"/>
                   <xsd:complexType name="foo_DT">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                        fe0bb241d2a011d9cd15e9729ee2f568
                        </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:sequence>
                             <xsd:element name="item" type="xsd:string">
                                  <xsd:annotation>
                                       <xsd:appinfo source="http://sap.com/xi/TextID">
                                fe0bb240d2a011d9acede9729ee2f568
                                </xsd:appinfo>
                                  </xsd:annotation>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="foo">
              <wsdl:part name="foo" element="p1:foo"/>
         </wsdl:message>
         <wsdl:portType name="foo_out_sync">
              <wsdl:operation name="foo_out_sync">
                   <wsdl:input message="p1:foo"/>
                   <wsdl:output message="p1:foo"/>
              </wsdl:operation>
         </wsdl:portType>
         <wsdl:binding name="foo_out_syncBinding" type="p1:foo_out_sync">
              <soap:binding xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <wsdl:operation name="foo_out_sync">
                   <wsdl:input>
                        <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
                   </wsdl:input>
                   <wsdl:output>
                        <soap:body xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" use="literal"/>
                   </wsdl:output>
              </wsdl:operation>
         </wsdl:binding>
         <wsdl:service name="foo_out_syncService">
              <wsdl:port name="foo_out_syncPort" binding="p1:foo_out_syncBinding">
                   <soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
              </wsdl:port>
         </wsdl:service>
    </wsdl:definitions>
    soap message incl. error
    <?xml version="1.0"?>
    <!-- see thedocumentation -->
    <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP:Body>
    <SOAP:Fault>
    <faultcode>SOAP:Server</faultcode>
    <faultstring>error during
    conversion</faultstring>
    <detail>
    <s:SystemError
    xmlns:s="http://sap.com/xi/WebService/xi2.0">
    <context>XIAdapter</context>
    <code>XMLScanException</code>
    <text><![CDATA[
    com.sap.aii.af.mp.module.ModuleException
    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
    (XISOAPAdapterBean.java:697)
    at
    com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl3.process
    (ModuleLocalLocalObjectImpl3.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process
    (ModuleProcessorBean.java:221)
    at
    com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0.process
    (ModuleProcessorLocalLocalObjectImpl0.java:103)
    at com.sap.aii.af.mp.soap.web.MessageServlet.doPost
    (MessageServlet.java:543)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service
    (HttpServlet.java:853)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet
    (HttpHandlerImpl.java:385)
    at
    com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleReques
    t(HttpHandlerImpl.java:263)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:340)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet
    (RequestAnalizer.java:318)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebConta
    iner(RequestAnalizer.java:821)
    at
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle
    (RequestAnalizer.java:239)
    at com.sap.engine.services.httpserver.server.Client.handle
    (Client.java:92)
    at com.sap.engine.services.httpserver.server.Processor.request
    (Processor.java:147)
    at
    com.sap.engine.core.service630.context.cluster.session.ApplicationSessio
    nMessageListener.process(ApplicationSessionMessageListener.java:37)
    at
    com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner
    .run(UnorderedChannel.java:71)
    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:94)
    at com.sap.engine.core.thread.impl3.SingleThread.run
    (SingleThread.java:162)
    Caused by: com.sap.aii.messaging.srt.BubbleException: error during
    conversion [null "null"]; nested exception caused by:
    com.sap.aii.messaging.util.XMLScanException: Parsing an empty source.
    Root element expected!
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
    (XMBWebServiceExtension.java:936)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.invokeOnResponse
    (XMBWebServiceExtension.java:602)
    at com.sap.aii.messaging.srt.ExtensionBubble.onMessage
    (ExtensionBubble.java:58)
    at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process
    (XISOAPAdapterBean.java:576)
    ... 20 more
    Caused by: com.sap.aii.messaging.util.XMLScanException: Parsing an
    empty source. Root element expected!
    at com.sap.aii.messaging.util.StreamXMLScannerImpl.open
    (StreamXMLScannerImpl.java:104)
    at com.sap.aii.messaging.mo.DefaultItem.setData
    (DefaultItem.java:294)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.makeItemFromPayload
    (XMBWebServiceExtension.java:972)
    at
    com.sap.aii.messaging.srt.xmb.XMBWebServiceExtension.onResponseToWS
    (XMBWebServiceExtension.java:879)
    ... 23 more
    ]]></text>
    </s:SystemError>
    </detail>
    </SOAP:Fault>
    </SOAP:Body>
    </SOAP:Envelope>

    Hi Klaus
    In your wsdl file the soap address tag (given below)
    <b><soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/></b>
    is to be edited as
    <b><soap:address location="http://xxxxxxxx:50000//XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out" /></b>
    because the soap address format should be like :
    <i>http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel</i>
    For more information :
    http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
    Hope this will be helpful.
    Regards
    Suraj

  • Problems with Soap Adapter

    Hi!
    I need to implement the following scenario:
    In SAP an user exit calls an RFC which uses a TCP/IP Connection (SM59) to the XI and sends data over this connection to it. The XI connects via a SOAP adapter my server program and sends the data in a soap stream to this server.
    This works sometimes ok and sometimes not.
    The status for those messages in the XI is "scheduled for outbound processing" with a little black arrow pointing to the right.
    The error message in the Runtime Workbench for such a job is:
    SOAP: request message entering the adapter
    SOAP: call failed
    SOAP: sending a delivery error ack ...
    SOAP: sent a delivery error ack
    How can I find out what the problem is?
    Thanks,
    Konrad

    Hi,
    When a message is scheduled for outbound processing, it is normally sent automatically.
    does it always sit at this status or does it change after a while ?
    If it is an issue with the connectivity from the Integration Server to the Adapter Framework you would get a different error message.
    If it is an issue with connectivity from the SOAP adapter to your target, you would also get a different error - it is likely to be shown as an outright failure. Plus the error shown in the message is likely to be
    "com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused"
    Hope this helps.
    i think you need to get Basis involved to see why messages are not getting sent from the rfc queues automatically all the time.
    Cheers
    Colin.

  • Web Service operation not in SOAP request

    Hi There,
    I have a problem with the SOAP receiver adapter.
    I have created an external definition and uploaded a wsdl file. Several messages have been created out of the file.
    In my mapping I fill the message structure from the wsdl file. When I send the message to the Web Service I get an error back.
    The reason for this error seam to be a missing tag under the SOAP:Body element. Because when I create a SOAP request with the XMLSPY, it looks like this:
    <SOAP:Body>
      <m:setVendor xmlns:m="http://..." ...>
        <ns8:v xmlns:ns8="http://...">
    But in the message from the XI adapter the <m:setVendor..> tag is missing:
    <SOAP:Body>
      <ns8:v xmlns:ns8="http://...">
    This m: tag seems to be the operation of the web service.
    Has anybody an Idea how to solve this?
    Is the error in the SOAP adapter or in the message definition?
    By the way, can I display the complete SOAP message that has been sent out from the adapter with any XI tool (including SOAP header)?
    BR,
    Jürgen

    Jurgen
    I have exactly the same problem in a RFC -> RFC Adapter -> XI -> SOAP Adapter -> Web Service scenario.
    What we see is that the external vendor wants the SOAP to be in "documet-literal wrapped" whereas XI is returning is as "document literal".
    **I don't want to change the original wsdl file because it was provided by our business partner and a modification could cause problems when release update.
    But I have build a workaround with an XSL stylesheet as a second mapping step in my Interface Mapping. The stylesheet adds the missing operation tag into the XML message.**
    Even in our case we dont want to change wsdl, the operation & soap body are going as two parts we want the soap body in operation,i think  this can be achieved by xsl stylesheet,Can u please brief us about xsl stylesheet as a second mapping step in interface maping.I dint work on xsl before......
    Advance thanx for ur help
    Sriram

  • Problem with SOAP Attachment in MM7

    Hi, I'm developing with Bea Weblogic 7 sp2 a MM7 server. My problem is when I add an attachment to SOAP message, Weblogic can't receive the message and say something as "The ID referenced by .... is unknow" but the href attribute in SOAP Message has the same value as the Content-ID of the attachment.
    The attachment is multipart/mixed. Please, I need help.
    I add here an old post from other user about this problem.
    <i>Hi
    I need some help for a problem I have with bea 7.0 sp1 web services.
    I'm trying to develop a SOAP Message Handler to intercept a SOAP Messages.It seems
    work properly for simple soap requests.
    But I need to send attachements so my request is like:
    POST /mm7/mm7Service HTTP/1.0
    Content-Type: multipart/related; type="text/xml"; start="<2ED4C017A7C250C35409DE82D1A8E6B1>";
    boundary="----=_Part_18_90248.1076664111251"
    Accept: application/soap+xml, application/dime, multipart/related, text/*
    User-Agent: Axis/1.1
    Host: xxx.xxx.xxx.xxx
    Cache-Control: no-cache
    Pragma: no-cache
    SOAPAction: "http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2?operation=Deliver"
    Content-Length: 5177
    ------=_Part_18_90248.1076664111251
    Content-Type: text/xml; charset=UTF-8
    Content-Transfer-Encoding: binary
    Content-Id: <2ED4C017A7C250C35409DE82D1A8E6B1>
    <?xml version="1.0" encoding="UTF-8"?>
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Header>
    <ns1:TransactionID soapenv:mustUnderstand="0" xsi:type="xsd:string" xmlns:ns1="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">E8D97EC0A80A712B5CF3C7E5A56AF121</ns1:TransactionID>
    </soapenv:Header>
    <soapenv:Body>
    <DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2">
    <MM7Version>5.3.0</MM7Version>
    <LinkedID>fa571b8e93C0A809513c33d383069dfb</LinkedID>
    <Sender>
    <RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
    </Sender>
    <Recipients>
    <To>
    <Number displayOnly="false">+123454678</Number>
    </To>
    <Cc>
    <RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
    </Cc>
    <Bcc>
    <RFC2822Address displayOnly="false">[email protected]</RFC2822Address>
    </Bcc>
    </Recipients>
    <Priority>High</Priority>
    <Content href="cid:74935BFBD687B557CE9C25A591FEE0DA" allowAdaptations="true"/>
    </DeliverReq>
    </soapenv:Body>
    </soapenv:Envelope>
    ------=_Part_18_90248.1076664111251
    Content-Type: multipart/mixed;
    boundary="----=_Part_17_2373292.1076664111231"
    Content-Transfer-Encoding: binary
    Content-Id: <74935BFBD687B557CE9C25A591FEE0DA>
    ------=_Part_17_2373292.1076664111231
    I implemented a simple Handler with a system.out in
    public boolean handleRequest(MessageContext mc)
    method
    But weblogic never gets there. It gives me this error instead:
    javax.xml.soap.SOAPException: failed to receive message:
    at weblogic.webservice.core.DefaultWebService.invoke(DefaultWebService.java:227)
    This seems related to this line
    <Content href="cid:74935BFBD687B557CE9C25A591FEE0DA" allowAdaptations="true"/>
    If I remove it, it can reach the handleRequest() method.
    Unfortunately I need the Content parameter....
    Does weblogic support href attributes in soap ?
    many thanks to whatever help
    (I already lost 3 days on that problem.....)
    alan</i>
    Thanks.

    Hello,
    Problem 1)
    In a previous question about this in SDN, someone (sorry, can't remember who) answered:
    "Have you or the user logged into the SAP GUI before? If not, have them login in. Our problems occured
    with new users that never logged into the SAP gui and so the user profile was never loaded with the ini
    file."
    Please try that.
    Problem 2)
    Are you sure it's running with the same variant in the background?
    What if you try every 5 minutes instead - maybe a minute is too short and it gets mixed up.
    You could also try copying RSWUWFML2 to ZRSWUWFML2, inserting an infinite loop and then attaching to it in order to debug it in the background.
    regards
    Rick Bakker
    Hanabi Technology

  • SOAP request error

    Dear XI Expertise,
    I am doing a scenario on SOAP>XI>System.....
    First thing my SOAP Adapter is not enabled when I see in the RWB-->Adapter Monitoring
    For this I searched the forum and followed almost all the blogs.......but could not find a solution......
    Especially in one blog thread I found one person has faced & been solved the same problem which I am facing. But for me it is not working......
    Here is the URL for that one...
    how can i enable SOAP Adapter?
    "In almost all the blogs, I found a solution given by some experts that when we send our first SOAP message, it will be automatically activated". But for me this is also not working.........
    I designed and configured my scenario in IR & ID and created a WSDL file for my outbound interface. Actually I created outbound interface from external definition (WSDL) which I got from EP side.....
    I used XML spy and created a "new SOAP request" from WSDL file which I generated from ID and given proper input in that message and sent the request.
    When I sent the request I got the following error message(dialog box)....
    HTTP error could not POST File
    ‘/XlSOAPAdapter/MessageServlet?channel=:LEGACYSYS_PRA_BS:WS_Sender&amp;version=3.O&amp;Sender.Service=LEGACYSYS_PRA_BS&amp;lnterIace=ns%3%2F%2Ffx.com%2Farchana%2Fwstorfc%5EPR_Out_MI’ on server ‘bcone-prd'(500).
    when I click ok, In the next dialog box I got this message
    "Error sending the SOAP data"
    Please help me out............
    Advance Thanks
    Praveen Gujjeti

    Praveen ,
    May I suggest a workaround till your SOAP adapter issue is not reolved?
    There are 2 URL's to which a SOAP message can be posted.
    1. You post it to the Adaptee Engine and the SOAP adapter then sends it to the Integration Engine.
    2. You post the message to the Integration Engine directly.
    The url you are now using is pointing to 1.
    Recreate the WSDL with the following URL-->
    <b>http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface></b>
    Click on Propose URL while defining the WSDL. More is on this blog,
    /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
    Let me know if it solves the problem partially?
    Regards,
    Bhavesh

Maybe you are looking for

  • Can I use adobe cc on my wife's computer which is networked to my computer

    I am using Adobe CC on my computer, but I sometimes use my wife's computer which is on the home network, there are only the 2 computers on the network.

  • IPod touch 3G won't work after falling in water? Help!

    Ok it's been 3 months since my iPod touch fell in the...toilet. I immediately put it in rice after pushing all the buttons. It was only in the water for a second. When I picked it up the screen was dim, flickering, then when black. I wiped it off and

  • How to make screenshot/jpg/pdf of ENTIRE long Safari window (not just visible part)?

    I want to get a "screenshot" (i.e. an image in any format -- PNG, JPG, PDF, whatever) of a looooooooong Safari window diplaying a Web page that entends far below the bottom of the visible screen area and has to be scrolled down to see all of it. I kn

  • Airport express 802.11 solid green but not working

    My airport express has been working for several months but will not now. I bought it to extend our internet to the upstairs as it was too far from out internet location. I have restarted it and moved to different outlets upstairs, but it will not wor

  • Client IP Address issues

    Just starting to put a Cisco Wireless infrastructure in place, currently just testing every thing.  Here is my issue. After I create a WLAN, bind it to the VLAN I can authenticate but can't get an IP address. Now if I bind the WLAN to the same VLAN t