Problem ABAP PROXY to SOAP

[#1]

I am developing an ABAP Proxy to SOAP interface.

I'm using an external definition with the wsdl for the service inbound interface and outbound interface for the determination, I was not allowed to use the definition as external error occurred while creating the abap proxy.

Thus, utilized a message type of structure to be sent, and a message maping.

However when I run the error message occurs:

/ Parsing / ADAPTER.SOAP_EXCEPTION - soap fault: No such operation 'mt_XXX_Request'.

Already confirmed URL of sending CC and left blank SOAP ACTION, however problem persists.

Already viewed this problem?

[former_member187533 · Accepted solution]

Hi!

Mapping the problem, I found a problem in mapping:

When I test the mapping with the default structure, works without problem with the headers:

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

<ns0:mt_XXX_Request xmlns:ns0="http://www.XXX.com.br/funcionario">

However when I copy the message coming from sxi_monitor, the header appears:

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

- <nm:mt_SPColab_Request Xmlns:nm="http://www.bravante.com.br/funcionario" xmlns:prx="urn:sap.com:proxy:D01:/1SAI/TAS337475E2AF22EC2AC09A:702">

Introducing the error:

Mapping:

Obrigado!

[Former Member · Accepted solution]

Hi Lucas - Is it your responce mapping? if so your webservice responce strcuture should be source and proxy should be your target right?

If it is request mapping, you don't need to worry about this mapping.

The error in the channel is complaining about responce mapping.

Refer to the below blog for a better understanding and compare your configuration.

http://scn.sap.com/people/anilkumar.bodapati3/blog/2013/07/07/proxy-to-soap-synchronous-scenerio-in-...

[Former Member · Accepted solution]

Hello,

>>However when I copy the message coming from sxi_monitor, the header appears:

Proxy adds this "xmlns:prx="urn:sap.com:proxy:D01:/1SAI/TAS337475E2AF22EC2AC09A:702" kind of prefix and namespace by default, but i don't think u should get error becoz of this?

In addition to that, ur XML declaration should be like this:

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

So, if u want u can test ur mapping again with correct request structure coming in moni.

Thanks

Amit Srivastava

[former_member187533 · Accepted solution]

Good afternoon !

So , I adjusted the structures and all MM and OP are OK . Even realize a test of the interface in Interface determination in Configuration using the XML coming from the proxy and they are ok .

However when I run the proxy keeps the problem :

  <SAP:AdditionalText> Com.sap.engine.interfaces.messaging.api.exception.MessagingException : SOAP : response message contains an error XIAdapter / parsing / ADAPTER.SOAP_EXCEPTION - soap fault : No such operation ' DOC ' < / SAP : AdditionalText >

This " DOC " would be the " header " of the mapping of WS .

This could be trouble for releasing firewall or communication with the WS ?

Thank you.

[Former Member · Accepted solution]

Hi Lucas - I think the problem is with your soap action. Did you configure the soap action as "DOC"?

If you don't have any operation leave that field as empty in the communication channel.

[Former Member · Accepted solution]

Hello,

Did u test ur WS using SOAP UI? - I have already asked this question

If not, then i would suggest you to do it and check if u are getting response or not?

If u are getting successful response from SOAP UI then open RAW tab in request and copy the action name in ur receiver channel and then test again.

But do remember to test it first fro SOAP UI.

Thanks

Amit  Srivastava

[former_member187533 · Accepted solution]

Thanks for the help!

With or without the SOAPAction configured and the error message is the same.

So when the testo SOAPUI works yes.

I did exactly this test, I took the RAW SoapUI and put in SOAPAction:

But:

This could be a problem to release the IP communication with the Legacy?

Thx!

[Former Member · Accepted solution]

Hello,

Is it possible for u to show me the RAW tab + SOAP Request for which u r getting correct response?

Thanks

Amit Srivastava

[Former Member · Accepted solution]

Hi Lucas - I don't think it has got something to with IP communication. I believe there is something wrong with the implimentation.

So when the testo SOAPUI works yes.

>>> Are you able to recieve the successful response when you test in Soap UI.

One more question : Have you imported the wsdl for your target strcture/manually created?

[Former Member · Accepted solution]

Hello,

One more point u can make use of TCP Gateway tool to check what exactly u are passing from PI and compare the same with SOAP UI request (message + header).

Thanks

Amit Srivastava

[former_member187533 · Accepted solution]

Hi!! Thanks for help!

Then, the test conducted by SOAPUI works:

Follows the RAW tab:

Hareesh Gampa,

The WSDL was imported through a URL released by the legacy system and imported into a external definition.

Thxxx!

[Former Member · Accepted solution]

Hi Lucas - i see another root tag "ATUALI***" in your requestxml which is not there in your target structure.

Your request strcture xml (from soap UI) should be same as output of the graphical mapping.

May be you can compare them and see what is missing.

[Former Member · Accepted solution]

Hello,

Eventually, I think i got u...

Ur WSDL file is correct + the way u are testing WS using SOAP UI is also correct, but the only thing which is wrong is u are not importing WSDL file in PI properly.

>> "<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>"

BTW, this line in WSDL file made me think that

So, try to re-import ur WSDL file as a "RPC Style WS" and then u will see ATUALIZIDOC" node in ur request message (u have to readjust ur request mapping)

Thanks

Amit Srivastava

[former_member187533 · Accepted solution]

Amit Srivastava,

Perfect! Actually this option solved my problem.

Many thanks for the help!

Best regards!

[Former Member · Accepted solution]

Glad to know that

BTW, just for information always try to debug calls in PI and TCP Gateway is one such tool to do that which could really help u in solving ur issues quickly.