ABAP-Proxy to SOAP: Error in SOAP Adapter

[Former Member]

Hi!

I would like to implement ABAP-Proxy to SOAP scenario.

Unfortunately my SOAP receiver channnel has the following error:

SOAP: call failed: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No SOAP Envelope but 1 definitions; HTTP 200 OK: java.io.IOException: No SOAP Envelope but 1 definitions; HTTP 200 OK

Furthermore the call of /sap/bc/soap/rfc of business system B is erroneous

http://<server system B>:8000/sap/bc/soap/rfc

Here I get the error: HTTP 500 Internal Server error

Can some one help me to solve this problem?

Thank you very much!

regards

Holger

[Former Member]

The error was the end of file BAPI_MATERIAL_EXISTENCECHECK_EC6CLNT200.wsdl.xml instead of

BAPI_MATERIAL_EXISTENCECHECK_EC6CLNT200.wsdl

[Former Member]

Hi,

Is it a Synchronous Scenario? It looks like the request is sent to your webService succesfully (HTTP 200 OK) but the response which is coming back is not valid SOAP response, may be envelope is missing.

You can try one thing, copy the target payload from your sxmb moni and test the webservice from a SOAP Client seperately using SAP SOAP client or any other tool and see what response you are getting back. This will help you resolve the error.

Also check your receiver SOAP Channel for the Conversion Parameters "Do Not USE SOAP Envelope" . See if it is cheked. By default it should be unchecked.

Thanks

Amit

[Former Member]

Hi!

Many thanks!

It is a a synchronous scenario.

2 questions:

1) do I need to generate a webservice?

2) Is it ok, that I cannot access to /sap/bc/soap/rfc/sap/

because I only have /sap/bc/soap/rfc/ ?

thank you!

[Former Member]

Hi Holger,

You don't need to generate a webservice. I guess your end system is a webservice that is why you are using SOAP Adapter.

You just need to give the payload, url, action, user, pwd (if any) in webservice client (as what you must have configured in your SOAP receiver channel) to test the webservice exposed by the end system.

It is fine if you are not able access the path /sap/bc/soap/rfc/

Amit

[Former Member]

Hi!

could you please tell me what are the technical steps I should to perform?

The problem is when I try to test the SICF-service /sap/bc/soap/rfc/

then the error comes up:

HTTP 500 Internal error

Thank you!

[Former Member]

Hi,

Might be possible the user or pwd is wrong or some other problem, but I guess this has nothing to do with the error you are getting. Just try testing the webservice as I told earlier. this will help you in figuring out the error.

Thanks

Amit

[Former Member]

Hi!

Could you tell me the format of target URL within SOAP receiver adapter channel?

Is it this one:

http://<server>:8000/sap/bc/soap/wsdl/?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200>;

Because in SAP XI book the other path will be recommended:

http://<server>:8000/sap/bc/soap/rfc/sap/BAPI_MATERIAL_EXISTENCECHECK?sap-client=200>;

Thank you!

[Former Member]

Hi,

Are you using the webservice exposed by SAP or it is third party webservice. Can you explain your complete scenario? What is the url you have given in your receiver SOAP Channel? Was that no configured earlier?

If at all you are using the SAP webservice, the wsdl link should be.

http://<server>:<http port>/sap/bc/soap/wsdl11?services=BAPI_MATERIAL_EXISTENCECHECK&sap-client=200 

The target url you will be able to see in the wsdl itself also

amit

[Former Member]

Hi Holger

500 internal error can be due to empty payload on test.

Check the URL& Soap action in the WSDL and use them in Receiver soap channel. It should work for you.

Thanks

Gaurav