Troubleshooting web services and outbound web service integrations

Learn how to solve problems that you may have when using web service integration steps in your services.

The following table describes some common problems that you might encounter when creating services that include web service and outbound web service integration steps:

Table 1. Common problems for the outbound web service integrations
Issue	Error message when you click Discover	Possible resolutions
Incorrect WSDL URI value	PARSER ERROR: Problem parsing '[path_name]\webAPIService.':The markup in the document following the root element must be well formed.	You have incorrectly typed the URI value. Navigate to the URI using a web browser to verify that you have the correct WSDL. A common problem is that the `?wsdl` argument is missing from the end of the URI. For file protocol URIs, the URI does not exist on disk. If you are unable to validate the location of the URI on disk, contact your network administrator.
Nonexistent host	Unknown Host Exception	You have incorrectly typed the host value. Navigate to the URI using a web browser to verify that you have the correct host information. The server that hosts the URI is offline (not running). Contact your network administrator to determine if this is causing the problem. The network is experiencing connectivity problems. Contact your network administrator to determine if this is causing the problem.
Authentication required for WSDL access	Runtime Exception: Unauthorized access to '[path_name]\webAPIService?WSDL'	The WSDL URI is protected by an authentication mechanism. If you have permission to access the web service, check the Protected WSDL check box, and then enter the Username and Password . Navigate to the WSDL URI using a web browser and save the text of the WSDL to a file so that you can use the file location as the target WSDL URI.
Invocation of the web service fails	org.apache.axis2.AxisFault: HTTP ( 500 ) Internal Server Error	The WSDL definitions in the cache are no longer compatible with the web service provider definitions. To fix this problem, clear the cache using the BPMClearWSICache command command.
Your business process, running on Linux, contains a series of outbound web services. The WSDL of your web service contains a large number of XML Schema Definition (XSD) files. When you discover the WSDL or generate data types in IBM® Process Designer, a failure occurs.	You have too many open files ...	IBM Business Process Manager requires more file handlers to load and parse a large WSDL file at a peak time. Your operating system, Linux, might not have enough file handlers available at that time. Increase the value of the nofile parameter in your /etc/security/limits.conf file. If your main WSDL file is calling many other WSDLs and XSDs, consider merging these files into one WSDL file.