Web Service Debugging Tips

Here are three tips to debug a web service created with USoft:

·	Configure a Rules Service, set the Log Level to: Debug, and start the Rules Service.

All statements executed are now written in the Rules Service log file.

·	Use the BenchMark Profiler. Before calling the web service, execute the following HTTP call:

http://<host>:<port>/<application>/<user>/xml-SOAP/SqlScript?$Password=<password>&$SQL=invoke RulesEngine.RuleProfilerStart

For example:

http://travelserver:4711/TRAVEL/TRAVELUSER/xml-SOAP/SqlScript?$Password=TrustMe&$SQL=invoke RulesEngine.RuleProfilerStart

Next, execute the web service call that you want to debug.

Then, stop the Profiler by executing the following HTTP call:

http://<host>:<port>/<application>/<user>/xml-SOAP/SqlScript?$Password=<password>&$SQL=invoke RulesEngine.RuleProfilerStop

In USoft BenchMark, you can now search for the latest profile.

·	When a web service provider is created, four files are generated: two .asp, one .inc and one .xml file.

The .inc file contains a DEBUG parameter. The default value of this parameter is No. You can use the DEBUG parameter to suppress or display messages regarding the setup of the web service provider (e.g. the rules service is not started or is using a different port number, the user/password are not valid, the rules service is not started on a specific application, the MSXML component is not installed,).

If the value of the DEBUG parameter is set to No, a generic error message is displayed:

The request was unsuccessful due to an unexpected condition encountered by the server"

If the value of the DEBUG parameter is set to Yes,a more detailed error message is displayed.