The following detail the steps needed for aiding in debugging problems that occur when WebFOCUS is accessing a Web Service:
As with any development environment that supports Web Services, the connectivity to the Web Service is only as current as the last time the WSDL file was consumed. If for any reason the Web Service has been modified, this would mean the WSDL file would have to be consumed again. If the changes to the Web Service were minimal, you can manually update the connection string by editing the edasprof.prf file from within the WebFOCUS Reporting Server Web Console. You can manually update the Master File and Access File with metadata changes.
Check to make sure that all the input parameters to the Web Service are being passed via the Report Selection criteria (WHERE command). If the Web Service is expecting certain values as input and these values are not set in the WebFOCUS Selection Criteria, zero records will be returned to WebFOCUS.
The transfer protocol for Web Services is usually HTTP. If the application that the Web Service is accessing is not up, an HTTP 404 error would probably be displayed.
FILEDEF SOAPOUT DISK c:\GetQuotesResponse.txt TABLE FILE GETQUOTES PRINT __RESPONSE WHERE SYMBOL EQ 'MSFT' ON TABLE HOLD AS SOAPOUT END
WebFOCUS |