SOAP: response message contains an error

[former_member206760]

Hi,

I am calling an external webservice in PI .

PI is creating a custom SOAP envelope and in the receiver soap channel I have ticked "Do not use SOAP envelope " . When I use the payload generated by PI in SOAP UI i am getting the reponse back...

But when I run through PI it gives the following error.

"SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error"

Payload generated by PI is as follows -

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

- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="https://www.mkdenial.com/types">

<soapenv:Header />

- <soapenv:Body>

- <ns0:SearchDpl xmlns:ns0="https://www.mkdenial.com/types">

- <ns0:credentials>

<ns0:Password>crown</ns0:Password>

<ns0:Username>guest</ns0:Username>

</ns0:credentials>

- <ns0:request>

<ns0:AlwaysIncludeUnknownCountry>true</ns0:AlwaysIncludeUnknownCountry>

<ns0:Connect>and</ns0:Connect>

<ns0:ExcludeCommonWords>true</ns0:ExcludeCommonWords>

- <ns0:Groups>

- <ns0:Group>

<ns0:Connect>and</ns0:Connect>

- <ns0:Matches>

- <ns0:Match>

<ns0:Field>NAME</ns0:Field>

<ns0:Keyword>FUT Test Customer</ns0:Keyword>

<ns0:Level>4</ns0:Level>

<ns0:Scope>Word</ns0:Scope>

<ns0:Type>Is</ns0:Type>

</ns0:Match>

- <ns0:Match>

<ns0:Field>STREET</ns0:Field>

<ns0:Keyword>National Drive</ns0:Keyword>

<ns0:Level>4</ns0:Level>

<ns0:Scope>Word</ns0:Scope>

<ns0:Type>Is</ns0:Type>

</ns0:Match>

- <ns0:Match>

<ns0:Field>CITY</ns0:Field>

<ns0:Keyword>Livermore</ns0:Keyword>

<ns0:Level>4</ns0:Level>

<ns0:Scope>Word</ns0:Scope>

<ns0:Type>Is</ns0:Type>

</ns0:Match>

- <ns0:Match>

<ns0:Field>STATE</ns0:Field>

<ns0:Keyword />

<ns0:Level>4</ns0:Level>

<ns0:Scope>Word</ns0:Scope>

<ns0:Type>Is</ns0:Type>

</ns0:Match>

- <ns0:Match>

<ns0:Field>COUNTRY</ns0:Field>

<ns0:Keyword>IN</ns0:Keyword>

<ns0:Level>4</ns0:Level>

<ns0:Scope>Word</ns0:Scope>

<ns0:Type>Is</ns0:Type>

</ns0:Match>

</ns0:Matches>

</ns0:Group>

</ns0:Groups>

</ns0:request>

</ns0:SearchDpl>

</soapenv:Body>

</soapenv:Envelope>

[VijayKonam · Accepted solution]

Problem is with the response. Check the response that you get when testing with SOAP UI. Looks like PI did not like it. THe test tools do not care about the format as long as they are valid XMLs.

VJ

[former_member206760 · Accepted solution]

Response message that i get in SOAP UI is as under-

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

<s:Body>

<SearchDplResponse xmlns="https://www.mkdenial.com/types">

<SearchDplResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

<Hits>

<DPLv2Entry>

<City/>

<Code>dos</Code>

<Country>XX</Country>

<DelistDate i:nil="true"/>

<EndDate i:nil="true"/>

<IDNUM>2556</IDNUM>

<LastUpdate>2005-12-05T00:00:00</LastUpdate>

<Name>BUSH, EDWARD JAMES</Name>

<Notes/>

<Source>DeniedPartyList</Source>

<StartDate>1988-07-18T00:00:00</StartDate>

<State></State>

<Street/>

<Url>https://www.mkdenial.com/view.cfm?idnum=2556</Url>

</DPLv2Entry>

</Hits>

<ReportDateTimeUTC>2011-08-16T14:05:14.7181511Z</ReportDateTimeUTC>

</SearchDplResult>

</SearchDplResponse>

</s:Body>

</s:Envelope>

[baskar_gopalakrishnan2 · Accepted solution]

I want you see any difference between response message structure between SOAP UI and PI response data structure. Also see any problem in the response mapping area... HTTP 500 could be due to some problem in mapping or application logic errror in target system and so... Please check.

[former_member206760 · Accepted solution]

Hi,

Yes ...actually th soap response is coming with the SOAP header . but PI response structure does not have it.

However I have written a response ABAP mapping to reomve it. So atleast it should show the response coming back into PI

I am not able to see the response in PI...

Also if the mapping is wrong...the payload generated by PI will not be working on SOAP ui

[baskar_gopalakrishnan2 · Accepted solution]

>Yes ...actually th soap response is coming with the SOAP header . but PI response structure does not have it.

There is the problem. Do you reference your abap mapping as the first mapping program before message mapping in the operation mapping area? Check do you see any mapping error in the runtime?

>Also if the mapping is wrong...the payload generated by PI will not be working on SOAP ui

Dont understand. SoapUI does not care about the response structure. Whereas PI really cares....

[former_member206760 · Accepted solution]

yes i am using ABAP mapping as the first mapping in the response...

also their is not mapping error in moni

[baskar_gopalakrishnan2 · Accepted solution]

Are you using abap mapping to remove the customer soap envelope and header things? Its a weird problem. Please find at what pipeline steps the response mesg processsing fails... Then we will decide.

[former_member206760 · Accepted solution]

yes i am using it to remove the envelope and header things...Also i wanted to make sure that PI response structure is not obstructing the response coming from the webservice and hence I used ABAP mapping...

When I see the response message coming from webervice it shows only 1 pipleline step -

Inbound Message

+SOAP header

+SOAP Body

but there is no response payload instead i am gettin the error

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error</SAP:AdditionalText>

[baskar_gopalakrishnan2 · Accepted solution]

Just check whether any firewall or port connection issues from the target system to PI too....

Looks like your mapping step does not takes place yet.....

Even xml validation step 1 does not take place....

Edited by: Baskar Gopal on Aug 17, 2011 1:07 PM

[former_member206760 · Accepted solution]

If there is a firewall/port issue why is the request part not giving error...

Is that something related to port opening for the direction of webservice to SAP??

[baskar_gopalakrishnan2 · Accepted solution]

Basically Pi does not start processing the response. If you have tcp gateway tool you can monitor the issues. I still want you to check with Basis team to see any server log about this message.

>Is that something related to port opening for the direction of webservice to SAP??

check with Basis team