Receiver SOAP adapter error

[Former Member]

Hi Experts,

We have an Idoc-SOAP scenario. when we uncheck the option "Do not use SOAP envelope" we are encountering an error with SOAP adapter and below is the error message :

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No task found for action "levisSupplierInputBean", object type "com.lsco.wc.interfaces.inbound.webservices.supplier", and object identifer "@dalpocapp4.lspoc.net".

But when we check the option "Do not use SOAP envelope",the message is succesfully processed by PI but the receiver system doesnot receive any values in the rspective fields.

The traget URL and SOAP action are correct and are verified by the receiver application team. Also the same web service works fine from SOAP UI and it create a vendor in the target system.

Please suggest why do we see the difference in behaviuor with the various options and between PI and SOAP UI.

Thanks,

Pragati

[former_member184681 · Accepted solution]

Hi Pragati,

It is also possible that you have specified an incorrect SOAP Action in the receiver CC. The error says namely:

No task found for action "levisSupplierInputBean"

Maybe this error is returned by the receiver system based on the fact that they are not able to interpret the SOAP Action properly. Check the action in the .wsdl file for the following:

<wsdl:operation name="AAA">

<wsdl:input Action="ActionName"/>

</wsdl:operation>

Hope this helps,

Greg

[Former Member · Accepted solution]

Hi Greg,

We have specified the action corresponding to the below tag :

<soap:operation soapAction= "Action Name">

This is verified by the receiver system team too. Also when we use the same action and use the property "Do not use SOAP envelope", the receiver system do receives our request but all fields are set to null.

Not sure if we are missing in config in PI.

Thanks,

Pragati

[markangelo_dihiansan · Accepted solution]

Hello,

This is verified by the receiver system team too. Also when we use the same action and use the property "Do not use SOAP envelope", the receiver system do receives our request but all fields are set to null.

Couple of questions:

1. Which SOAP version is the receiving system using SOAP 1.1 or 1.2 ?

2. Which HTTP version are they using HTTP 1.0 or 1.1?

Regards,

Mark

[Former Member · Accepted solution]

Hi Mark,

It's SOAP 1.1 and HTTP 1.1

Thanks,

Pragati

[former_member184681 · Accepted solution]

Dear Pragati,

>> the receiver system do receives our request but all fields are set to null

This seems to be a hint here. Make sure that your SOAP Envelope is correctly formed, and what is most important, that all tags are created in correct namespaces. It might so happen that your receiver system does not read your call just because the tags are missing the namespace definition. This is because tag XXX with no namespace definition is not really the same one as tag XXX under namespace YYY.

Hope this helps,

Greg

[markangelo_dihiansan · Accepted solution]

Hello,

HTTP 1.1

Are you sure it is HTTP 1.1? Because if this is the case, you can only enable HTTP 1.1 by using SOAP Axis and there are some bean configurations for that. See SAP Note 1039369 FAQ XI Axis Adapter for more information.

Can you share the HTTP Headers (under the Raw Tab for Request in SOAP UI)?

Hope this helps,

Mark

[Former Member · Accepted solution]

Hi Mark,

Below is the raw tab data for request from SOAP UI:

POST http://XXXXX/Windchill/servlet/RPC HTTP/1.1

Accept-Encoding: gzip,deflate

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

SOAPAction: "urn:ie-soap-rpc:com.wc.interfaces.inbound.webservices.supplier!fetchSupplierDetails"

User-Agent: Jakarta Commons-HttpClient/3.1

Content-Length: 3105

Authorization: Basic

Host: XXXXXXXXX

The Style of the webservice is "RPC" whereas we have other services with style as "Document". Do you see any issue due to this. We are looking into the SAP note.

Thanks,

Pragati

Edited by: Pragati Divekar on Mar 5, 2012 10:39 AM

[markangelo_dihiansan · Accepted solution]

Hello,

The Style of the webservice is "RPC" whereas we have other services with style as "Document". Do you see any issue due to this. We are looking into the SAP note.

Thanks for pointing this out. The SAP Note that you should be referring to is Note 856597 - FAQ XI 30 PI 70 PI 71 SOAP Adapter.

See the answers to these questions:

Q: Does the RPC or Document style in WSDL play a role in the SOAP
adapter?
and
Q: Can I convert an RPC styled WSDL to a document styled WSDL?

Basically, you just need to implement the payload in PI exactly as it is in SOAP UI.

PS: The SAP Note contains attachments about the two WSDL styles.

Hope this helps,

Mark

[Former Member · Accepted solution]

Hi Mark,

Our issue is resolved. We reimporrted the wsdl file using the option "RPC style" in external definition and this resolved the issue.

Thanks for your inputs.

Regards,

Pragati

[baskar_gopalakrishnan2]

This is sync scenario. The problem is when you send the request without soap envelope you could pass it to the target system and processing failed at the target system level. The error shows that you are having response message errror. THis tells me that target system sends the structure which you dont have it in the pI response structure or the target system sends SOAP Header which PI cannot able to ignore or process it. You need to talk to target system and verify whether they need SOAP header details. If so check the soap envelope option and send the request message. Similarly handle the same in response message.