cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with the SOAP SND Receiver and a problematic SOAP request

Former Member
0 Kudos

Hello,

Let me explain the problem.

In the Simple Object Access Protocol (SOAP) 1.1

W3C Note 08 May 2000

link: http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383500

is stated under 4.3 SOAP Body

'A body entry is identified by its fully qualified element name, which consists of the namespace URI and the local name. '

In our internal test we always use a soap request like this:


<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
	<SOAP-ENV:Body>
		<ORDERS05>
			....
		</ORDERS05>
	</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Here the body has a qualified namespace.

Unfortunately in the customer request is like this:


<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/">
	<Body>
		<ORDERS05>
			....
		</ORDERS05>
	</Body>
</Envelope>		

I try this SOAP envelope in our internal test and it is not working. The offical SOA protocol needs a namespace in the body element and it seems that the SAP Pi needs that to.

A soap request without the namespace in the body element causes this error:


http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry über die Verbindung SOAP_http://sap.com/xi/XI/System. Grund: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during parsing of SOAP header

Can I fix this problem in the SOAP request before the message is forwarded from the adapter engine to the integration engine?

Best regards,

Nils Kloth

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Dear Prateek,

the error is from the messagemonitoring in the adapter engine. So the integration engine is called from the adapter engine.

Best regards,

Nils

prateek
Active Contributor
0 Kudos

As per my understanding u have problem at Soap sender where the sopa client sends request in incorrect soap format. Please confirm.

If u r using the URL

http://kas052.hauni.koerber.de:8036/sap/xi/engine?type=entry

then this would mean that you are posting the data directly to the integration engine. The adapter engine can't be used in this case.

Regards,

Prateek