SOAP - XI - SOAP

[Former Member]

Hi All,

I had configured a SOAP XI SOAP scenario with QOS EO. I executed it twice. At that time it was working. In the third run, it displayed NO_RECEIVER_CASE_ASYNC. Thats NOT the main problem. Then I looked at the message.

Here<i> in the Sender Interface field, it was showing my Sender Namespace. And in the "Sender Namespace" field, it was showing "Sender Interface"</i>

Its odd but it is there.

Thanks

Greg

[Former Member]

can you check ur sender soap adapter configurations. and the URL

[stefan_grube]

In your configuration, did you place the interface name to the namespace field and vice versa?

That happens to me very often, as the fields are in a different order as in all other configuration places.

Regards

Stefan

[Former Member]

Ya you have to put interface name and namespace

Otherwise the pipeline service wont recognize the messages coming to XI.

And there should be a receiver agreement configured for that combination.

Thanks

Sebin

[Former Member]

Hi ,

Jusr check the WSDL you have imported for receiver interface and the configuration you have done in receiver adapter .

For more details refer to following blog .

/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi

Thanks ,

Suvarna

Award pts if it helps .

[Former Member]

WSDL for receiver could not be questioned, coz its throwing error after inbound binding

Greg

[Former Member]

Any more comments

[Former Member]

Even i was facing this problem once.

Wat i did tat times is i jus Checked my message structure n all..

Have you created the structure using XSD only right..

Stilll the problem was not done.,,,

So i asked the basis to restart the SOAP Adapter..

And it started working after that

Hope this may help you...

Thanks

Sebin

[Former Member]

Hi Greg,

Its really surprising that how can we change the fields data in the configuration?? May be check again , it may be problem with the something like buffer or not updated correctly.

Warm Regards,

Vijay