Layer7 API Management

  • 1.  How to detect a bad SOAP operation?

    Posted 02-14-2018 04:23 PM

    We had some new people on our project attempt to setup a service endpoint in the GW and then hit it via SoapUI to learn how to write and test policies.  When it looked like they had everything correct they tried sending the request to the GW but got back a URL not resolved error.  They had exactly the correct URL in the service endpoint definition and in their SoapUI tests.  We tracked it down to their soap operation was not properly coded in the soap request in SoapUI.  This was a rather time consuming trial and error process due to the misleading nature of the GW error message.  We did not find any logs that contained any additional information that might have led us to the soap operation being the error.  What would be the best way to debug this type of error?  Can we turn up logging, look in different log files, change options in the GW to make debugging this type of error quicker?

  • 2.  Re: How to detect a bad SOAP operation?
    Best Answer

    Broadcom Employee
    Posted 02-15-2018 04:12 PM

    Hi Rick,


    I would suggest setting up a 'catch all' policy as described here: How to set a default response when a service cannot be found and Include the 'Audit Messages in Policy' assertion.


    Now when the request includes an unsupported operation you will see this logged:


    3212: Resolved "APIMSOAPService" service (#8791f00c032d44e7935795b5fe733259) but request does not match any operation in the service's WSDL