Skip to Content

Last week I was given a synchronous wsdl and asked to develop a sync-sync interface (SOAP-Proxy). I imported it in ESR, developed the interface and was all set to test.

I opened SOAP UI, imported the wsdl and started mock service. Triggered proxy message from ECC.

And boom –

HTTP 500 Internal Server Error


Then I revisited all the configurations, felt everything is fine. Retested the scenario. And again – 500 exception

I tried to get the logs from SOAP UI. Found the below error:

ERROR: An error occured [Missing operation for soapAction [] and body element……


I’ve set Require SOAP Action property to ‘False’ in SOAP UI and tested. – Same issue again.

I was wondering where could be error. When I investigated the wsdl I found that SOAP binding was Remote Procedure Call (RPC) style. Generally, we use document style binding.

/wp-content/uploads/2014/09/1_546237.png

  

In external definitions in ESR when we import a wsdl, by default Messages option will be set to “From All Available Message Definitions”

/wp-content/uploads/2014/09/2_546238.png

  

But, when we import wsdl with RPC style binding, we have to change it to “Using RPC Style”.

/wp-content/uploads/2014/09/3_546245.png

  

Finally, when I made these changes, my scenario was successful.

More info: https://help.sap.com/saphelp_nwesrce/helpdata/en/43/ce993b45cb0a85e10000000a1553f6/content.ht

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply