Collect troubleshooting data for web services problems in IBM Business Process Manager
You are having a web service problem with IBM Business Process Manager. You would like to know what documentation you must collect (MustGather) so that the IBM Business Process Manager Support team can diagnose your problem. If you gather this documentation before contacting support it will expedite the troubleshooting process, and save you time.
Diagnosing the problem
Collect the MustGather information for Web Services problems in IBM Business Process Manager. Gathering this information before calling IBM support helps in understanding the problem and saves time when analyzing the data.
Business Process Manager has two different ways to use Web Services. Business Process Manager Standard and Express make use of Web Service Integration components, SOAP message connector components and Web Service components. These are created using the Process Designer tooling. These components will be referred to as Standard Web Services Components.
Business Process Manager Advanced can also utilize those methods, but also allows for using Web Service Import and Export components, which are created using the Integration Designer tooling. These components will be referred to as Advanced Web Services Components.
|Setting the trace string|
Web Services problems using Advanced Web Services Components:
Set the trace string to
Web Services problems using Standard Web Services Components:
Set the trace string to *=info:WLE.*=all: com.ibm.ws.websvcs.*=all
If the Web Services issue is involving Web Services Security, please see the following Web Services Security Mustgather:
Note: Enabling the trace might slow down your system. This delay can lead to transaction time-outs and errors.
To set the tracing and generate a new set of logs and traces, complete the following steps:
- Under Troubleshooting > Log and Trace, pick the server where you want to change the settings.
- Click Change Log Detail Levels.
- Select the configuration tab to set the tracing. This change takes effect after the next server restart and a completely new set of log files can be collected. Optionally, select the runtime tab to dynamically set the tracing.
- Enter the trace string and click OK.
- If you selected the configuration tab, stop the server.
- Archive and delete the current logs/traces/ffdc from the following directories:
- Start the server and check the trace.log file to make sure that the correct tracing is set.
- Reproduce the problem and gather the complete server log files and ffdc directory.
- Delete the trace string from the Log Detail Level for your server.
Note: Ensure that you have set the Maximum trace file size (recommendation: 20MB) as well as the number of historical trace files (recommendation: 10) to an appropriate value. You can find those values at Servers > Application Servers > server_name > Diagnostic Trace Service.
|General diagnostic information|
Collect the general MustGather information as described in Collect troubleshooting data for the IBM Business Process Manager products.
In addition, provide the following information for web services problems:
- An export of the project (either a .twx file or a Project Interchange file)
- Sample SOAP request and response message
- WSDL file for the web service being invoked, including any included WSDL and/or XSD files
- Is this an inbound Web Service?
- Is this an outbound Web Service?
- Check WSDL for WS-I compliance
- If using Standard Web Services components, is the Web Service Integration or SOAP message connector being used?
- Is Web Services security and/or SSL being used for this service?
|What to do next|
- Review the logs and traces at the time of the problem to try to determine the source of the problem.
- Use IBM Support Assistant to search for known problems in the information center, forums, and technotes.
- If you cannot find related problems or cannot solve the problem, send the information you have collected to IBM by following the instructions in Exchanging Information with IBM Technical Support.
|Business Integration||IBM Business Process Manager Express||Web Services||Linux, Windows||8.5.7, 8.5.6, 8.5.5, 22.214.171.124, 126.96.36.199, 8.5, 188.8.131.52, 184.108.40.206, 220.127.116.11, 8.0.1, 8.0, 18.104.22.168, 22.214.171.124, 7.5.1, 126.96.36.199, 7.5|
|Business Integration||IBM Business Process Manager Standard||Web Services||AIX, Linux, Solaris, Windows||8.5.7, 8.5.6, 8.5.5, 188.8.131.52, 184.108.40.206, 8.5, 220.127.116.11, 18.104.22.168, 22.214.171.124, 8.0.1, 8.0, 126.96.36.199, 188.8.131.52, 7.5.1, 184.108.40.206, 7.5|
|Business Integration||IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server||Web Services||220.127.116.11, 8.0.1, 8.0|
More support for:
IBM Business Process Manager Advanced
Software version: 7.5, 18.104.22.168, 7.5.1, 22.214.171.124, 126.96.36.199, 8.0, 8.0.1, 188.8.131.52, 184.108.40.206, 220.127.116.11, 8.5, 18.104.22.168, 22.214.171.124, 8.5.5, 8.5.6, 8.5.7
Operating system(s): AIX, Linux, Solaris, Windows
Reference #: 1593461
Modified date: 26 June 2012