Soap Receiver Adapter Error. Pls advice urgent

Hi All,
While using Soap Receiver Adapter for synchronous communication
*My Soap Request is:*
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
<strFrom>XI</strFrom>
</ns1:SendMessage>
*My Soap Response from server is:*
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Inbound Message
-->
<tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<return xsi:type="xsd:int">-1</return>
<strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
</tns:SendMessageResponse>
How to resolve the error.
Regards

Henry,
Your xml message is not xsd compliant...see if you can generate a xml message using your wsdl with random values, compare that to your imcoming msg..and thats your issue..
Hope that helps
Regards
Ravi Raman
Reward points if helpful !

Similar Messages

  • HTTP Sender and HTTP Receiver adapter. Pls advice urgent

    Hi All,
    There is one Third Party that wants to send XML data and receive XML data with XI.
    Please let me know can I use HTTP for that.
    How to use HTTP Sender part?
    How to use HTTP Receiver Adapter?
    Pls send blogs/doc for that
    Thanks and Regards

    hi.,
    Check this thread for the code for a HTTP Client,
    /message/266750#266750 [original link is broken]
    Also, check these blogs. They use HTTP adapters for their configuration,
    /people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
    /people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Check these links for the configuration part.
    http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
    Weblog :
    /people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - although this weblog is
    aimed at explaining the sync-async bridge.. Sriram has taken http-to-file scenario as the example
    note:reward points if solution found helpfull.....
    regards
    chandrakanth.k

  • SOAP Receiver adapter error. SOAP CALL Failed

    Hi ,
        I am implementing scenario R/3->RFC adapter->XI->SOAP REceiver adapter->Web Service (Synchronous). I am getting the error.
    SOAP: call failed
    SOAP: error occured: java.net.ConnectException: Connection timed out
    Message log is as below.
    Any clue ?
    Thanks & Regards,
    Mathew
    2005-10-31 18:59:58
    Success
    output
    1130810398454
    The message was successfully received by the messaging system. Profile: XI URL: http://host:Port/MessagingSystem/receive/AFW/XI
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Using connection AFW. Trying to put the message into the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398458
    Message successfully put into the queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message was successfully retrieved from the request queue.
    2005-10-31 18:59:58
    Success
    output
    1130810398459
    The message status set to DLNG.
    2005-10-31 18:59:58
    Success
    output
    1130810398460
    Delivering to channel: CC_CALCULATOR
    2005-10-31 18:59:58
    Success
    output
    1130810398564
    SOAP: request message entering the adapter
    2005-10-31 19:03:07
    Success
    output
    1130810587497
    SOAP: call failed
    2005-10-31 19:03:07
    Error
    output
    1130810587497
    SOAP: error occured: java.net.ConnectException: Connection timed out
    2005-10-31 19:03:07
    Error
    output
    1130810587498
    Exception caught by adapter framework: Connection timed out

    Hi Mathew,
    Check if the webservice is availble??? Based on the error below, it looks like the message is timing out at the Adapter Engine level waiting for the connection to make the webservice call...
    Prasad

  • HTTP adapter. Pls advice urgent

    Hi,
    Some cleint wants to send data to PI (7.0)  through HTTP.
    Now should that client send through HTTP or it can also use
    HTTPS.
    Pls advice urgent.
    Regards

    Hi,
              All XI runtime components using the HTTP protocol support the encryption of the HTTP data stream by means of the SSL protocol, also known as HTTPS. HTTPS data streams are completely transparent to the Exchange Infrastructure
         HTTPS (Hyper Text Transfer Protocol Secure) is a secure version of the Hyper Text Transfer Protocol (http). Secure means of transferring data using the https protocol in the World Wide Web where secure ecommerce transactions, such as online banking transactions and other financial transactions are involved.
    Https encrypts the session with a digital certificate i.e., HTTP over SSL (Secure Sockets Layer) which can be used by Web browsers and HTTPS - capable client programs.
    If the website begins with https:// instead of http://, it is a secure site. Almost 99% of the browsers can connect to web servers either using http or https. The address bar in the browser will begin with https instead of http, if a web site is secured.  
    HTTPS Protocol work with the combination of programs including the browser programs which takes care of the encryption/decryption routines that exist on the web hosting servers.
    HTTP data is sent over TCP/IP port 80, whereas  HTTPS  data is sent over port 443.
    HTTPS comes in two flavors, both ensuring the confidentiality of data sent over the network
    1)Server authentication :
    Only the HTTP server identifies itself with a certificate that is to be verified by the client.
    2)Client authentication:
    Additionally, the HTTP client identifies itself with a certificate that is to be verified by the server
    Regards,
    sangeetha

  • WebService Receiver Problem. Pls advice urgent.

    Hi All,
    I have R/3 (RFC) -- XI -- R/3(WebService) Scenario.
    Now when I test my WebService in R/3 using wsadmin command it works fine.
    But If I import my webservice as wsdl file and use it in Soap Receicer Adapter and use XI I get error:
    <SAP:Category>XIAdapterFramework</SAP:Category>
    <SAP:Code area="MESSAGE">GENERAL</SAP:Code>
    <SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: sapd03ci.alkhaliji.bank</SAP:AdditionalText>
    Pls advice very urgent
    regards

    Hi RAC,
    May I know where this R/3 webservice located.
    In your landscape or not?
    Thanks
    Gujjeti

  • SOAP receiver adapter error using Google Search web service

    Hi all,
    I'm trying to connect and old 4.5b system to XI SP16 to make it receive information from external Web Services.
    My scenario is made up of a sender RFC adapter and a SOAP receiver which is sending the message to the Google web service (http://api.google.com/GoogleSearch.wsdl) and then awaiting a response from it.
    I'm stuck with this error: "No Deserializer found to deserialize a ':key'". The problem is that XI is sending this kind of message:
              <m:doGoogleSearch xmlns:m="urn:GoogleSearch" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <key>mykey</key>
                   <q>testing</q>
                   <start>0</start>
                   <maxResults>1</maxResults>
                   <filter>true</filter>
                   <restrict>String</restrict>
                   <safeSearch>true</safeSearch>
                   <lr>String</lr>
                   <ie>String</ie>
                   <oe>String</oe>
              </m:doGoogleSearch>
    while Google is expecting this:
              <m:doGoogleSearch xmlns:m="urn:GoogleSearch" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                   <key xsi:type="xsd:string">mykey</key>
                   <q xsi:type="xsd:string">testing</q>
                   <start xsi:type="xsd:int">0</start>
                   <maxResults xsi:type="xsd:int">1</maxResults>
                   <filter xsi:type="xsd:boolean">true</filter>
                   <restrict xsi:type="xsd:string">String</restrict>
                   <safeSearch xsi:type="xsd:boolean">true</safeSearch>
                   <lr xsi:type="xsd:string">String</lr>
                   <ie xsi:type="xsd:string">String</ie>
                   <oe xsi:type="xsd:string">String</oe>
              </m:doGoogleSearch>
    with explicitly declared xsi:type.
    I've tested both messages with XMLSpy and the first one is always returning the same error.
    Is there a way to make XI send an XML message with written xsi:type?
    Many thanks in advance!
    Max

    Hi Ricardo!
    I followed your suggestion to create a simple XSLT mapping program (in the ABAP stack) and I added it to the Interface Mapping in the Integration Repository. The result is exactly the soap message that the Google web-service is expecting.
    I'm attaching the XSLT code below in case somebody has the same problem... thanks again for your hint!!
    Regards!
    Max
    <xsl:transform version="1.0"
      xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:sap="http://www.sap.com/sapxsl"
    >
    <xsl:strip-space elements="*"/>
    <xsl:template match="/">
    <ns1:doGoogleSearch xmlns:ns1="urn:GoogleSearch" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
          <key xsi:type="xsd:string"> <xsl:value-of select= "//key"/> </key>
          <q xsi:type="xsd:string"> <xsl:value-of select= "//q"/> </q>
          <start xsi:type="xsd:int"> <xsl:value-of select= "//start"/> </start>
          <maxResults xsi:type="xsd:int"> <xsl:value-of select= "//maxResults"/> </maxResults>
          <filter xsi:type="xsd:boolean"> <xsl:value-of select= "//filter"/> </filter>
          <restrict xsi:type="xsd:string"> <xsl:value-of select= "//restrict"/> </restrict>
          <safeSearch xsi:type="xsd:boolean"> <xsl:value-of select= "//safeSearch"/> </safeSearch>
          <lr xsi:type="xsd:string"> <xsl:value-of select= "//lr"/> </lr>
          <ie xsi:type="xsd:string"> <xsl:value-of select= "//ie"/> </ie>
          <oe xsi:type="xsd:string"> <xsl:value-of select= "//oe"/> </oe>
       </ns1:doGoogleSearch>
    </xsl:template>
    </xsl:transform>

  • HTTP Receiver Adapter. Pls advice

    Hi All,
    I have response from System A already present in XI.
    I need to send the response from System Aa present in XI to other System B through HTTP Receiver adapter in synchronous manner means that System B should send response back to XI.
    Can HTTP Receiver adapter be used for Sync Communication in my scenario.
    Please send blogs/link for it
    Regards

    Hi Henry,
    Refer the below links:
    http://help.sap.com/saphelp_nw04s/helpdata/en/85/78af1bf407434796aaf8dbd6d4e7b7/frameset.htm
    Re: HTTP Sender - how to read URL Parameter USER id into Mapping
    /people/amol.joshi2/blog/2006/06/28/must-fire-a-http-get-from-xi---try-this
    http://help.sap.com/saphelp_nw04/helpdata/en/82/f4993c03e0cd37e10000000a11405a/frameset.htm
    http://sap-ag.com:8088/sap/xi/adapter_plain?service=sender&namespace=urn%3Asap-ag%2Ecom&interface=%2Fsap%2Forders
    http://sap-ag.com:8088/sap/xi/adapter_plain?service=sender&namespace=urn%3Asap-ag%2Ecom&interface=%2Fsap%2Forders&qos=EO&msgguid=3C61F6C12F1E2DD1E10000000A1145AB
    Thanks,
    Satya Kumar
    Reward points if it is useful..
    Edited by: SATYA KUMAR AKKARABOYANA on Apr 15, 2008 10:26 AM

  • SOAP receiver adapter error

    Hi all.
    I have create a FM ZRFC_FILENUMBER on R/3 side. Then i created webservice in the R/3 itself for this RFC. It gave me WSDL file. I have loaded this WSDL file in XI external definitions.
    In the receiver adpater configuration i am using the URL as specified in the file.
    e.g.: http://erpdevmil.xyz.in:8001/sap/bc/srt/rfc/sap/ZRFC_FILENUMBER?sap-client=200&wsdl=1.1
    I have tried using XML spy. It works fine,communicates with R/3 and sends data back. All well. But doesn't work in actuall scenario.
    Acutal scenario is : Created Proxy in R/3 side and sending data to this webservice and expects data back from webservice. Here it fails.
    In audit log it shows as follows :
    Success SOAP: request message entering the adapter with user J2EE_GUEST
    Error SOAP: call failed: java.net.ConnectException: Connection timed out: connect
    I have gone through lots of blogs and threads. As per experts, checked the URL and operation name N number of times. Now want something which can solve my problem . Please it's urgent.
    Thanks in advance.
    Regards,
    Kavan Shah

    U can trace ur SOAP call with the tool TCPGateway.
    /people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway
    In the request and response section of the TCPGateway trace, u ll view the appropriate error.
    Also make sure that ur webservice is accessible in the network from XI.
    Regards,
    Prateek

  • SOAP Receiver Adapter Error in XI RWB - java.lang.NULLPointerException

    Hi,
    We have a asynchronous scenario in SAP-XI, where we are sending the PO data from SRM to third party (Hubspan / TNT). Proxy is being used at Sender side and SOAP Adapter is used for Receiver Communication Channel.
    u2022SRM is sending around 1000 messages through background job and around 995 or 996 messages are being processed successfully and showing the proper XML payload as well in RWB. But 4-5 messages are getting failed in XI RWB for u2018java.lang.NullPointerExceptionu2019. For these failed messages we are not able to see the XML payload as well in XI RWB while these messages are showing successful status in MONI in SRM and XI and we are able to see the payload as well in MONI. The webservice is restarting and trying to send the payload three times in RWB, but it is getting the same Nullexception error.
    04.11.2011 16:45:49.715 Success Delivering to channel: CC_B2B_HUBSPAN_RCV
    04.11.2011 16:45:49.715 Success MP: Entering module processor
    04.11.2011 16:45:49.715 Success MP: Processing local module localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    04.11.2011 16:45:49.716 Success SOAP: request message entering the adapter with user J2EE_GUEST
    04.11.2011 16:45:49.716 Success SOAP: Target url: https://connect.hubspan.net/mh/server/tp=NMHG/ssid=DAA6F0E9AC1000BD03A41B363BBFD676
    04.11.2011 16:45:49.999 Error SOAP: call failed: java.lang.NullPointerException
    04.11.2011 16:45:49.999 Success SOAP: sending a delivery error ack ...
    04.11.2011 16:45:49.999 Success SOAP: sent a delivery error ack
    04.11.2011 16:45:49.999 Error SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
    04.11.2011 16:45:49.999 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException
    04.11.2011 16:45:50.000 Error Exception caught by adapter framework: null
    04.11.2011 16:45:50.022 Error Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
    04.11.2011 16:45:50.037 Success The message status set to WAIT.
    u2022If we are resending the failed message from XI RWB, it is getting failed again with the same error. On the other hand if we are initiating the message again from SRM to Hubspan for the same PO, it is getting processed successfully in RWB but still not showing XML payload in RWB.
    u2022If we are getting the payload from XI MONI for the failed message and doing a test with component monitoring in RWB, it is working fine.
    Please help me to solve this issue.
    Thanks
    Sumit

    Hi Sumit,
    From my experience, when you transfer  SAP POs through PI to external webservice, there should be some validation happens at the webservice layer of the target system before the web service passes the original information to  their application layer. The validation can be anything like checking the Vendor address, Checking the correctness of the order ...etc etc . So i would suggest to ask your external web service folks to check if they have any validation in place before they pass the data to their application layer.
    As you said only some POs/XMLs are failing, i strongly feel that this could be the issue.
    Please note if you receive response code other than 200 from webservice, SOAP adapter treats that as error and send the same message back to AE.
    Normally webservices won't send 200 code for any validation error
    PS: you can still try to use XMLSpy to post the failed message to the web service to know the exact cause.

  • Queue gets blocked in Receiver System . Pls advice urgent

    Hi All,
    When I send data from CRM --- XI --- DM system
    Whenever data comes at DM system everytime queue gets blocked and gets status "SYSFAIL".
    Pls tell me how to solve this problem.
    Regards

    1.You can use transaction codes SMQR and SXMB_ADM for queue status resetting.
    2.Use transaction codes SMQ1 and SMQ2 for deleting SYSFAIL files, and manually resending messages in the queues.(For activating queues in SMQ1 and SMQ2, you would need to first deregister them in SMQR or SXMB_ADM).
    3.As a pre-requisite, the IS configuration parameter MONITOR QRFC_RESTART_ALLOWED should be set to 1.
    /people/prashanth.azharuddin/blog/2006/11/24/some-errors-in-an-xi-production-environment
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

  • SOAP receiver adapter message: PI payload in parameter or body

    Hi,
    We tried to send messages via the following way to an external partner: SAP --> IDoc > XI (7.1)> HTTP(s) --> external partner.
    We tried 2 techniques:
    1. using a HTTP receiver communication channel with HTTP destination (using certificate).
      As the path prefix in the destination, including parameters,  exceeds 256 characters, we had to search for another solution
    2. using the SOAP receiver communication channel with a target URL (https string) and indicator 'Do not use SOAP envelope' set   
      When sending the message, the body of the message, the IDoc XML payload doesn't seem to be read by the partner, probably related to the fact that they do not use the right software to do so, as decribed in forum: 
    SOAP receiver adapter error (SOAP receiver adapter error.)
    Is this the right interpretation and is there no other solution than try to append the payload to the parameterlist ?
    Regards,
    Jan Macken

    The partner found a way to read the body correctly

  • Soap Response Error. Pls advice urgent

    Hi All,
    I am using Soap Receiver Adapter.
    *My Soap Request is:*
    <?xml version="1.0" encoding="UTF-8" ?>
    - <ns1:SendMessage xmlns:ns1="urn:MMWebSrvService">
      <strUsername>XIWSDL</strUsername>
      <strPassword>XIWSDL</strPassword>
      <strFrom>XI</strFrom>
      <strTo>123</strTo>
      <strMessage>abc</strMessage>
      <strSubject>333</strSubject>
      <strService>/SMPP/1</strService>
      <nOptions>0</nOptions>
      </ns1:SendMessage>
    *My Soap Response from server is:*
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <tns:SendMessageResponse xmlns:tns="urn:MMWebSrvService" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:types="urn:MMWebSrvService/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <return xsi:type="xsd:int">-1</return>
      <nIndex xsi:type="xsd:int">0</nIndex>
      <strErrorDescription xsi:type="xsd:string">String reference not set to an instance of a String. Parameter name: s</strErrorDescription>
    </tns:SendMessageResponse>
    Does anyone has idea of the above error?
    I have also got one link:
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=818243&SiteID=1
    Regards

    Henry,,
    Take a look at this...
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=818243&SiteID=1
    you are getting a error response back from your soap partner..you have to have them to fix it..The above link is good if they are using dot net which is what i think it is..
    Regards
    Ravi Raman

  • Soap Receiver Adapter problem. very urgent..

    Hi,
    When I am sending data from XI to CRM through soap receiver communication channel I am getting error:
    Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Authority check failed
    Pls advice urgent.
    Regards

    Hi Rick,
    At fist did  you create SOAP fault message mapping in your scenario?
    If not then plz do that.
    Some links for ur help:
    Troubleshooting - RFC and SOAP scenarios *** Updated on 20/04/2009 *** - have a look into this to troubleshoot your SOAP
    Fault Message Types - A Demo (Part 1)
    Receiver SOAP adapter scenarios:
    RFC -> XI -> WebService - A Complete Walkthrough (Part 1)
    RFC -> XI -> WebService - A Complete Walkthrough (Part 2)
    Regards,
    Vinod.

  • Same Sender and Receiver File Name. Pls advice urgent

    Hi All,
    My sender file name is auto generated number so
    it is dynamic in nature.
    ex. "abc1.txt"
         "abc2.txt"
    Now In my Sender File Adapter I cannot give
    File Name hard coded as my sender file name is auto generated number.
    Also I want same file name received at receving end.
    File Sender --   "abc1.txt"
    File Receiver -- "abc1.txt"
    File Sender --   "abc2.txt"
    File Receiver -- "abc2.txt"
    Pls advice.
    Regards

    Hi Rider,
    All your sender files have .txt extension but the name is not constant(dynamic in nature).Than in this case to pick ur file u can use the *.txt as ur sender file name.Than all the files with .txt extension in the source folder specified would be picked.
    Than u can proceed in the same way given in this blog
    /people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
    Please let me know if u need any information
    Thanks,
    Bhargav
    Note:Award points if found useful

  • No SOAP Envelope error in SOAP Receiver Adapter

    Hello Friends,
    Informaiton:-
    I have configured one Synchronous scenarion for SAP R/3 to PI 7.1 to Java based web applicaiton.
    On the Receiver/Outbound side, i have configured the SOAP Receiver Adapter with the Target URL and SOAP Action.
    Outbound and Inbound service interfaces have Request/Response and Fault messages.
    Issue:-
    While sending the Message, Below error is noticed in ABAP stack SXMB_MONI during the Call Adapter Stage and also in RWB (Channel Monitoring) .
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: No SOAP  Envelope but 1 {}RESPONSES; HTTP 200 OK
    I also found that Request message is not reaching to the Java Web server.
    I am taking the Same message Payload (found at Call Adapter Stage) and ussing it in XML Altova SPY Web client tool. There it is running scuccessfully and getting the Response message.
    please suggest.
    Thanks & Regards
    Jagesh

    Hi,
    Yesterday i consumed the same WSDL file in Altova XML SPY and there it is working, getting the Response.
    Now comparing the SOAP Request message reaching to the Third party Web server (which fall within the same Lane network)
    from SAP PI and Altova XML SPY tool. I used TCP Gateway for the below scenarios.
    (1)First i sent the SOAP message from PI and observed the RESPONSE message without the SOAP Envelope in TCP Gatway Trace and hence i am getting the No SOAP Envelope Error in PI.
    (2)I consumed the same WSDLfile in Altova XML SPY and sent the SOAP message, here i got the Proper SOAP Response message and hence success in this case. (Used the same Data Payload as used in point 1)
    (3)Now to identify the issue in the SOAP Request message being sent from PI, i used the same SOAP message sent in step 1 here, that means copy the entire SOAP ENvelope from the TCP gateway Trace and pasted it in Alota Spy and sent, there it is found running (got the response message from Third Party server).
    One difference i found in HTTP Protocol statements in SOAP Request message in Point no 1 and Point no 2 above.
    HTTP Protocols in Point 1 (Through PI).
    POST  HTTP/1.0
    Accept: /
    Host: 172.24.138.142:4544
    User-Agent: SAP-Messaging-com.sap.aii.af.sdk.xi/1.0505
    CallingType: SA
    content-id: <soap-00306EEAC2051ED1839136CEE8564900 sap.com>
    Content-Type: text/xml; charset=utf-8
    Content-Length: 1195
    SOAPACTION: "Action1"
    HTTP Protocols in Point 2 (Through Altova).
    POST / HTTP/1.1
    Content-Type: text/xml
    User-Agent: XML Spy
    SOAPAction: "Action1"
    Host: 172.24.138.142:4544
    Content-Length: 1195
    Connection: Keep-Alive
    Cache-Control: no-cache
    Thanks to Mr. Stefan Grube for writting such a nice blog.
    Troubleshooting SOAP, HTTP and Mail Adapter Scenarios with TCPGateway
    Experts, please suggest me further.
    Thansk & Regards
    Jagesh

Maybe you are looking for