cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP query

Former Member
0 Kudos

Hi,

I am doing a idoc-soap scenario.

I am creating the soap envelope manually using xsl mapping.

In the receiver soap adapter, I have checked the "donot use soap adapter" check box.

Everything seems to be working fine.

My outbound payload as seen using the MDT is:

--SAP_04c24541-4c8a-11db-97b2-0002559ad50b_END

Content-ID: <soap-04c245404c8a11dbaea00002559ad50b@sap.com>

Content-Disposition: attachment;filename="soap-04c245404c8a11dbaea00002559ad50b@sap.com.xml"

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

Content-Description: SOAP

<b><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='0' SOAP:mustUnderstand='1'><sap:MessageClass>ApplicationResponse</sap:MessageClass><sap:ProcessingMode>synchronous</sap:ProcessingMode><sap:MessageId>ab9152e1-4c89-11db-cbe7-0002559ad50b</sap:MessageId><sap:RefToMessageId>44f7788f-20bf-006c-0000-0000911aa04f</sap:RefToMessageId><sap:TimeSent>2006-09-25T11:33:31Z</sap:TimeSent><sap:Sender><sap:Party agency='' scheme=''></sap:Party><sap:Service>SOAPRECEIVER</sap:Service></sap:Sender><sap:Receiver><sap:Party agency='' scheme=''></sap:Party><sap:Service>UPSERTACC_BPM</sap:Service></sap:Receiver><sap:Interface namespace='urn:horizon:sfdc03'>MI_UPSERTACC</sap:Interface></sap:Main><sap:ReliableMessaging xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:QualityOfService>BestEffort</sap:QualityOfService></sap:ReliableMessaging><sap:HopList xmlns:sap='http://sap.com/xi/XI/Message/30' SOAP:mustUnderstand='1'><sap:Hop timeStamp='2006-09-25T11:33:31Z' wasRead='false'><sap:Engine type='AE'>af.dx5.abc</sap:Engine><sap:Adapter namespace='http://sap.com/xi/XI/System'>XIRA</sap:Adapter><sap:MessageId>ab9152e1-4c89-11db-cbe7-0002559ad50b</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:att-ab9152e04c8911dba3fe0002559ad50b@sap.com'><sap:Name>MainAttachment</sap:Name><sap:Description>Main document</sap:Description><sap:Type>Application</sap:Type></sap:Payload></sap:Manifest></SOAP:Body></SOAP:Envelope>

--SAP_04c24541-4c8a-11db-97b2-0002559ad50b_END

Content-ID: <att-ab9152e04c8911dba3fe0002559ad50b@sap.com>

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

<?xml version="1.0" encoding="UTF-8"?>

<i>(soap envelope created using xsl)</i>

<i><soapenv:Envelope</i> 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" xmlns="abc"><soapenv:Body><upsertResponse><result><created>false</created><errors xsi:nil="true"/><id>001T0000003tzr9IAA</id><success>true</success></result></upsertResponse></soapenv:Body><i></soapenv:Envelope></i>SAP_04c24541-4c8a-11db-97b2-0002559ad50b_END

An extra soap envelope seems to be added(the highlighted part)even when the "donot use soap envelope" is checked.

Could anyone explain why this is happening?

Thanks,

Smitha.

Message was edited by: Smitha Rao

Accepted Solutions (1)

Accepted Solutions (1)

stefan_grube
Active Contributor
0 Kudos

What you see in MDT is the whole XI message consisting of the XI message header and the payload. There is no special monitor where you can see how the SOAP message looks like.

In your case the SOAP adapter sends the payload unchanged to the receiver.

Regards

Stefan

Answers (2)

Answers (2)

Former Member
0 Kudos

Smitha,

Did you get the solution for the problem? If you have already solved your problem please let us know how you handled it because I am also facing the same problem.

Thanks,

Venkat

Former Member
0 Kudos

Hi Smitha

I think that you also have to add the parameter "nosoap=true" to the end of the target URL in the communication channel.

Nik