RFC to SOAP Scenario - WSDL-Import really needed?

[Former Member]

Hey @all,

we like to feed a webservice via SAP Backend. As middleware we use SAP PI 7.1.

The planned scenario is RFC to SOAP. The wsdl of webservice (NON-SAP) has no filled soapAction-Parameter and the operation with name "process" occures three times in it with the same name, but each operation "process" has it's own Request / method (axis), like "Request1", "Request2", "Request3". Each request has it's own response.

In this case it is not possible to import the wsdl as external references correctly - the import gaves an error caused of the identical names of the three operation-parameters.

The question is:

Is it possible to work this out without the import of wsdl and without soapAction-Parameter?

How could we call the correct operation?

Thanks very much in advance,

Stefan

[markangelo_dihiansan · Accepted solution]

Hi,

Maybe you could try to editing the WSDL and import it three times e.g for process (1) here is the WSDL (1) --> Make sure you delete the other process.

Make message mapping for each process and its corresponding response. So that would be, 6 message mappings (request and response) and 3 operation mappings.

In Integration Directory, call the correct operation in Interface Determination by using xPath.

http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination

although the blog above is for receiver determination, the xPath conditions for interface determination are the same.

For the without SOAP Action parameter, I guess it is okay to leave blank. I have not used the SOAP Axis though (I used the PLAIN_HTTP adapter for that). Just to be sure, test it in SOAP UI.

Hope this helps,

Mark

[Former Member · Accepted solution]

Hi Mark,

thank you for your answer.

We've asked our webservice provider to touch the wsdl and change the names of the identical operation names.

Furthermore we find out that we could not build up all the nested items correctly in that way which they are included in wsdl.

Makes it scence to build this up with message and data types?

We've asked our provider to change that too. In case of they don't change it, maybe its better to change the scenario to "RFC to http", so we could build up all the nested items correctly and code the xml structre.

Many greetings,

Stefan

[stefan_grube]

> The wsdl of webservice (NON-SAP) has no filled soapAction-Parameter

That is OK.

> and the operation with name "process" occures three times in it with the same name,

This is not OK.

"The name attribute of the input and output elements provides a unique name among all input and output elements within the enclosing port type."

http://www.w3.org/TR/wsdl#_names

Request a valid WSDL.