HTML( AXIS ) Receiver Channel / WS with Empty Response

[ckocyigit]

Hello experts,

I'm quite new to PO so upfront I'm sorry if I'm missing something very simple or completly off the track.

I tried to google it to best of my abilities but I just couldn't find a solution.

My scenerio is SAP ERP - PO - 3rd Party WS.

I was getting security exceptions so I started using HTML( AXIS ) transport protocol instead of HTML protocol of SOAP adapter.

I was able to get past the security exceptions after setting the channel as below but the response message when I view from sxmb_moni is "almost" empty and there are no exceptions.

I'm able to get the full response from SOAP UI though.

If I change the "SOAP Action" to something else I get the exception below:

The message with Action 'randomstuff' cannot be processed at the                           receiver, due to a ContractFilter mismatch at the EndpointDispatcher.

If I change the "user" parameters value I get the exception below:

At least one security token in the message could not be validated.

So I'm thinking my request is reaching the 3rd party service, but I'm losing the response payload somewhere.

Here is what I need to do at SOAP UI to get a response successfully:

1. Set "WSS-PasswordType" to "PasswordText"

2. Set Authorization to "Basic" and enter username and password.

3. Fill the request.

I downloaded and imported the wsdl to Enterprise Services Builder from the same link so I'm not sure if there can be a type mismatch at response.

And below is the response I get when I use PO by SPROXY TCode at ERP with the same request:

<?xml version="1.0" encoding="UTF-8"?>
<ns0:EkstreSorgulamaResponse xmlns:ns0="http://tempuri.org/"/>

Any pointers will be much appreciated but please keep in mind that I'm quite new to PO.

Thanks in advance,

Cagalp.

[ckocyigit · Accepted solution]

Hello,

for anyone who might experience the same thing, we resolved this by changing the imported wsdl and using same configuration as the first post.

by my senior umutkarabay 's advice,

we edited the wsdl as below:

Before:

<xsd:element name="EkstreSorgulamaResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EkstreSorgulamaResult" type="q2:HesapEkstreResponse" minOccurs="0" nillable="true" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>

After:

<xsd:element name="EkstreSorgulamaResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EkstreSorgulamaResult" type="q2:HesapEkstreResponse" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>

Thank you pavankumar.d for your reply again.

Have a nice day,

Cagalp.