How to handle multiple inbound interfaces with WSDL messages

[Former Member]

Hi All,

We have a synchronous: Abap Proxy -> XI -> WebService Scenario. The webservice has multiple SoapActions e.g. SearchForProduct_WithX, SearchForProduct_WithY each with different message types. We have tried to use the receiver determination to send the request to the correct soapaction using conditions e.g. if field X in the request is populated use SearchForProduct_WithX action/message.

But when we run it through the proxy we get this error:

  <CODE>IF_DETERMINATION.TOO_MANY_IIFS_CASE_BE</CODE> 
  <ERRORTEXT>Multiple inbound interfaces not supported for synchronous calls</ERRORTEXT>

Does anybody know how we can get around this or how best to deal with the multiple soap actions per wsdl situation.

[prateek]

For ur synchronous scneario, u cannot use conditions in receiver determination. The reason being for the synchronous scenario without BPM, u must have only 1 receiver. So instead of using the condition in receiver detrmination, go for enhanced interface determination option.

Regards,

Prateek

[Former Member]

Hi Prateek,

Thanks for the good info. Can you please give a little more info on how you use enhanced interface determination for a WSDL that has multiple SOAP actions.

Cheers

Luke

[Former Member]

Luke,

For synchorouse case does not this "Multiple inbound interfaces not supported for synchronous calls".

you have only action.

[Former Member]

Hi Luke,

You say you used the Receiver Determination to determine which SOAP action to use. Does this mean that you have configured different receiver Services for each action? Or did you use the Interface Determination to determine which SOAP action to call?

[Former Member]

Hi Yaghya,

We have used conditions in the Interface Determination. Interestingly if we use an HTTP sender adapter we can use this configuration ... but once we try and use ABAP proxies we get the previous error.

Another related question ... when we use the http adapter we get a connection time out exception. Same thing happens if we try and use the wsdl tester at /wsnavigator but we can open the wsdl through the browser. Any idea on this one?

Thanks for all your help.