Re: IWS problems

By any chance have you given the IBM Integrated Web Services Server's built in server tracing capabilities a try in order to gather more information?

You can access the server tracing capabilities via. the IBM Web Administration for i interface (http://<hostname>:2001/HTTPAdmin). Click on the Manage tab, Application Servers sub tab, and expand the Server Properties section on the left side of the Web page. Click the Server Tracing link under the Server Properties section and you will see the available options (on the right) for turning on SOAP message tracing, toolbox tracing, and web services run-time tracing. Perhaps this will give you some more information regarding the incoming Web services request that isn't working. Just remember to disable the tracing once you are done with it in order to keep log files small. Chances are the SOAP message tracing will be the most beneficial to you.

Ryan Watkins

On 10/21/2010 09:22 AM, James H. H. Lampert wrote:

Back to our customer who wants to communicate with our product via web
services.

It seems that they are attempting to call one of the web services I
hastily deployed a month ago, and they're calling it from Visual BASIC.NET.

1. It seems that the web service is throwing a number format exception,
but we can't tell which parameter it's throwing it on. (Other than
obviously one of the ones coded as numeric.)

2. For all of the parameters specified as "decimal," they're also
finding a "specified" field associated with the parameter. Anybody have
the slightest idea what that's about?

--
JHHL