TroubleShooting: Web Services engine problems for versions 5.0, 5.1, and 6.0
 Technote (FAQ)
 
Problem
Troubleshooting for Web Services engine problems in WebSphere® Application Server. This should help address common issues with this component before calling IBM® support and save you time.
 
Solution

Troubleshooting MustGather Problem Determination Submitting
Troubleshooting documents provide component descriptions and common problems with solutions.

Getting background information on Web Services

Web services technology allows two different applications to communicate, regardless of programming language or platform.

Resources to learn more about Web services:
WebSphere Application Server Information Center
http://www.ibm.com/software/webservers/appserv/was/library/

IBM Education Assistant
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp


TroubleShooting steps to help resolve Web Services engine problems

1. Have you tried upgrading to the latest maintenance level of WebSphere Application Server?
  • If yes, continue to Question 2.
  • If no, upgrading to the latest maintenance level may resolve your problem. There have been numerous fixes for the Web Services engine and tooling. Please see this document for more information about upgrading.

2. Is Apache SOAP or Apache Axis being used?
  • If yes, please be aware that Apache SOAP has been deprecated. Users are encouraged to migrate any Apache SOAP or Axis applications to the IBM Web Services engine.
    • This article explains how to migrate from Apache SOAP.
    • This article explains how to migrate from Apache Axis.
    • This article explains Axis support in WebSphere Application Server.
  • If no, continue to Question 3.

3. Are you having trouble packaging Xerces and Xalan with your Web Service client or provider?
  • If yes, then review this technote.
  • If no, continue to Question 4.

4. Are you having interoperability problems with .NET?
  • If yes, ensure that the messaging style is document/literal. The rpc/encoded messaging style does not work with .NET clients. Also, .NET clients do not support the same attachments protocol as WebSphere Application Server. For more tips on interoperability, see Chapter 10: "Web Services Interoperability" in the IBM WebSphere Version 6 Web Services Handbook.
  • If no, continue to Question 5.

5. Are you having problems with an EJB exposed as a Web Service?
  • If yes, confirm that you are able to invoke the EJB independent of the Web Service client.
  • If no, continue to Question 6.

6. Are Java Collection types being used?
  • If yes, please be aware that using Java Collection types will cause interoperability problems. JAX-RPC 1.0 and 1.1 do not provide mappings for all of the Java Collections. For more information, see this technote. For a workaround, please see this article.
  • If no, continue to Question 7.

7. Are you having a problem with command line tools?
  • If yes, please review this article for troubleshooting suggestions.
  • If no, continue to Question 8.

8. Are you having a problem with compiled bindings?
  • If yes, please review this article for troubleshooting suggestions.
  • If no, continue to Question 9.

9. Are you experiencing serialization or deserialization problems?
  • If yes, please review this article for troubleshooting suggestions.
  • If no, continue to Question 10.

10. Are you having a problem with a Web Service client?
  • If yes, please review this article for troubleshooting suggestions.
  • If no, continue to Question 11.

11. Are you having a problem with Web Services Security?
  • If yes, please review this article for troubleshooting suggestions. Also note that WS-Security is not supported for unmanaged clients.
  • If no, continue to Question 12.

12. Is the problem occurring with a Web Services application within WebSphere Studio Application Developer (WSAD) V5.1.2?
  • If yes, please be aware that there are many known limitations with WSAD V5.1.2, which are documented here.
  • If no, continue to Question 13.

13. Is the problem occurring with a Web Services application within WebSphere Studio Application Developer Integration Edition (WSAD IE)?
  • If yes, please be aware that there are many known limitations with WSAD IE, which are documented here.
  • If no, continue to Question 14.

14. Review the WebSphere Application Server V5, V5.1, or V6.0 Info Center, or the WebSphere Application Server Support site for additional information that may help you to resolve the problem.

What to do Next?
If the above steps did not solve your problem, see the MustGather for Web Services problems to continue investigation.
 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Web Services (for example: SOAP or UDDI or WSGW or WSIF)
Operating system(s): Windows
Software version: 6.1
Software edition:
Reference #: 1243045
IBM Group: Software Group
Modified date: Jul 31, 2006