Proxy to SOAP Asynchronous, Issues in the receiver communication channel

[Former Member]

Hi All,

We have a proxy to Webservice Scenario(SOAP). Where we are facing issue in the receiver communication channel with the following error.

  Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.

   Adapter Framework caught exception: null

MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException

This is the error from the Audit Log.

We have tested the wsdl file int the SOAP UI - No error

And tested the mapping part - No error.

Connection - No error. We are able to connect the Webservice.

<wsdl peration name="UpdateCategory">

<wsdl:input wsaw:Action="http://tempuri.org/ICatalogService/UpdateCategory" name="UpdateCategoryRequest" message="tns:UpdateCategoryRequest" />

<wsdl utput wsaw:Action="http://tempuri.org/ICatalogService/UpdateCategoryResponse" name="UpdateCategoryResponse" message="tns:UpdateCategoryResponse" />

We have given input SOAP action "http://tempuri.org/ICatalogService/UpdateCategory" at configuration.

Even after thorough checking we are still at a lost on this error. Has anyone come across such or can shed any light upon this? Thanks in advance, Your inputs are most welcomed.

[Shabarish_Nair]

refer http://scn.sap.com/community/pi-and-soa-middleware/blog/2008/01/08/troubleshooting--rfc-and-soap-sce... and check your settings

[Former Member]

Hi Shabarish,

I checked the blog. But didn't find any issue related with "

failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException.

   Adapter Framework caught exception: null" .

In this issue, We are able to connect the webservice, Deliver the message. BUT the delivered message to the webservice team doesn't come with any namespace associated with it. That's the issue we are facing.

Thanks & Regards,

Rajesh.S

[Shabarish_Nair]

Check the payload send via SOAP UI and compare it with the PI payload. If the namespace is not coming you might have to handle it in a mapping and add the extra namespace.

[markangelo_dihiansan]

Hello,

Is the scenario you have configured really asynchronous? Since it is seen in the WSDL definition for update category that it has both a request and response message.

Regards,

Mark

[Former Member]

Hi,

Can you please guide us on how to handle it in the mapping by adding the namespace (http://tempuri.org)  ?

Thanks in Advance,

Rajesh.S

[Former Member]

HI Mark,

Yes we are using asynchornous, Only request we are using.

Regards,

Rajesh.S

[Former Member]

Hello Mark,

Yes, We are using asynchronous, As only request we are using.

Regards,

Rajesh.S