SOAP vs SOAP Axis

[Former Member]

Hi,

Need some help please. I have configured a RFC to SOAP scenario to call web service. The web service is developed using Axis. I configured the SOAP receiver comm channel - specifying the SOAP action, but It is failing with the error that soap action is invalid.

So I tried to change to use SOAP Axis - but this requires deployment of the SOAP Axis adapter. We are using XI 3.0. Somehow the basis guy is still unable to get the Axis adapter up. When i tested using the axis servelet, it is showing error with 3 missing components...

Qns : is it possible to just use SOAP receiver comm channel to call Axis web service? if yes, how may it be done? I compared the XI request vs sample request (using soapui) : the soapui request has this xml tag :

<Ser : name of the webservice operation>.

<data of the request>

</Ser>

But the XI request is missing the <ser> parts. Is it possible to add this in using SOAP adapter?

Thanks for any advice.

[Former Member · Accepted solution]

Add on to my query :

Soapui request looks like this :

<ser:getCustAcctHierarchyDtls soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<searchCriteria xsi:type="wses:CustHierarchySearch" xmlns:wses="http://pegasus/WsEsm">

<custAcctNo xsi:type="xsd:string"></custAcctNo>

<custAcctNoType xsi:type="xsd:string"></custAcctNoType>

<billAcctNo xsi:type="xsd:string"></billAcctNo>

<billAcctNoType xsi:type="xsd:string"></billAcctNoType>

<svcNo xsi:type="xsd:string">BBRO8882</svcNo>

<svcType xsi:type="xsd:string"></svcType>

<custAcctId xsi:type="xsd:string"></custAcctId>

<billAcctId xsi:type="xsd:string"></billAcctId>

<svcInstId xsi:type="xsd:string"></svcInstId>

</searchCriteria>

</ser:getCustAcctHierarchyDtls>

This is request generated from XI :

<?xml version="1.0" encoding="UTF-8" ?>

- <ns1:searchCriteria xmlns:ns1="http://pegasus/WsEsm">

<ns1:custAcctNo>A</ns1:custAcctNo>

<ns1:custAcctNoType>A</ns1:custAcctNoType>

<ns1:billAcctNo>A</ns1:billAcctNo>

<ns1:billAcctNoType>A</ns1:billAcctNoType>

<ns1:svcNo>A</ns1:svcNo>

<ns1:svcType>A</ns1:svcType>

<ns1:custAcctId>A</ns1:custAcctId>

<ns1:billAcctId>A</ns1:billAcctId>

<ns1:svcInstId>A</ns1:svcInstId>

</ns1:searchCriteria>

The XI request is missing <ser> & </ser> parts. Can this be added in using SOAP? Or it will be done automatically using SOAP Axis?

[Former Member · Accepted solution]

Hi,

Could it be that you imported your RPC styled WSDL without using the RPC-style import mode?

As long as the payload is generated incorrectly as the result of this, neither adapter can repair the payload on the fly.

Best regards, Yza

[Former Member · Accepted solution]

Hi,

yep, that was what happened. I didn't update the thread here earlier. But what happened was I should have loaded wsdl using RPC format. Thanks for answering anyway.