Skip to Content
0
Feb 24, 2014 at 07:08 PM

How to remove all standard SOAP content like Content-ID:, Content-Description

477 Views

Hi ,

can you please let me know how to remove standard SOAP content from messages

I am posting below text file via SOAP adapter:

POST /hapld/tos/kdwhapltos HTTP/1.1

Host: www.pld.ups.com

Content-type: multipart/mixed; boundary=BOUNDARY

Content-length: 719

--Boundary

CA12345 *qweru* wefgh*

--Boundary--

But below content automatically added into a messages even I am using don’t use SOAP envelop ,I don't want to keep all below information in my messages content

Content-ID:<soap-7228e9329d7a11e3800a00000086498a@sap.com>

Content-Type:text/xml; charset=utf-8

Content-Disposition:attachment;filename="soap-7228e9329d7a11e3800a00000086498a@sap.com.xml"

Content-Description:SOAP

<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><sap:Main xmlns:sap='http://sap.com/xi/XI/Message/30'

versionMajor='3' versionMinor='1' SOAP:mustUnderstand='1'>

<sap:MessageClass>ApplicationMessage</sap:MessageClass><sap:ProcessingMode>synchronous</sap:ProcessingMode>

<sap:MessageId>72232e3c-9d7a-11e3-a92f-00000086498a</sap:MessageId><sap:TimeSent>2014-02-24T17:38:17Z</sap:TimeSent>

<sap:Sender><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'></sap:Party><sap:Service>DE2CLNT200</sap:Service></sap:Sender>

<sap:Receiver><sap:Party agency='http://sap.com/xi/XI' scheme='XIParty'>UPS PLD UPSPLD_In_A http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>ExactlyOnce</sap:QualityOfService></sap:ReliableMessaging><sap:System xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Record namespace='http://sap.com/xi/XI/Message/30/general' name='interfaceDeterminationGUID'>69e207999d7a11e3c20e00000086498b</sap:Record><sap:Record namespace='http://sap.com/xi/XI/Message/30/general' name='syncTimeout'>1200000</sap:Record><sap:Record namespace='http://sap.com/xi/XI/Message/30/general' name='senderAgreementGUID'>204a48791a5c30188698c82c7a5ac51f</sap:Record></sap:System><sap:DynamicConfiguration xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Record namespace='http://sap.com/xi/XI/Message/30/routing' name='InterfaceDeterminationHash'>76ffb8570fb621f090b46490ec701f6a</sap:Record><sap:Record namespace='http://sap.com/xi/XI/Message/30/general' name='senderAgreementGUID'>204a48791a5c30188698c82c7a5ac51f</sap:Record></sap:DynamicConfiguration><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Hop timeStamp='2014-02-24T17:38:17Z' wasRead='false'><sap:Engine type='AE'>af.di3.ch00vdi3s</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>72232e3c-9d7a-11e3-a92f-00000086498a</sap:MessageId></sap:Hop><sap:Hop timeStamp='2014-02-24T17:38:18Z' wasRead='false'><sap:Engine type='AE'>af.di3.ch00vdi3s</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>729468d1-9d7a-11e3-8cb7-00000086498a</sap:MessageId></sap:Hop></sap:HopList></SOAP:Header><SOAP:Body><sap:Manifest xmlns:sap='http://sap.com/xi/XI/Message/30' xmlns:xlink='http://www.w3.org/1999/xlink'><sap:Payload xlink:type='simple' xlink:href='cid:payload-7247d2779d7a11e38da500000086498a@sap.com'><sap:Name>MainDocument</sap:Name><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope>Content-ID:<payload-7247d2779d7a11e38da500000086498a@sap.com>

Content-Disposition:attachment;filename="MainDocument.txt"

Content-Type:multipart/mixed; boundary=BOUNDARY

Content-Description:MainDocument