WebSphere Application Server - Express, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Troubleshooting the Web Services Invocation Framework

Before you begin

For information on resolving WebSphere-level problems, see Diagnosing and fixing problems.

Why and when to perform this task

To identify and resolve Web Services Invocation Framework (WSIF)-related problems, you can use the standard WebSphere Application Server trace and logging facilities. If you encounter a problem that you think might be related to WSIF, you can check for error messages in the WebSphere Application Server administrative console, and in the application server stdout.log file. You can also enable the application server debug trace to provide a detailed exception dump.

A list of the WSIF run-time system messages, with details of what each message means, is provided in Message reference for WSIF.

A list of the main known restrictions that apply when using WSIF is provided in WSIF - Known restrictions.

Here is a checklist of major WSIF activities, with advice on common problems associated with each activity:

Create service
Handcrafted WSDL can cause numerous problems. To help ensure that your WSDL is valid, use a tool such as WebSphere Studio to create your service.
Define transport mechanism
For the Java Message Service (JMS), check that you have set up the Java Naming and Directory Interface (JNDI) correctly, and created the necessary connection factories and queues.
For SOAP, make sure that the deployment descriptor file dds.xml is correct - preferably by creating it using WebSphere Studio or similar tooling.
Create client - Java code
Follow the correct format for creating a WSIF service, port, operation and message. For examples of correct code, see the Address Book Sample.
Compile code (client and service)
Check that the build path against code is correct, and that it contains the correct levels of JAR files.
Create a valid EAR file for your service in preparation for deployment to a Web server.
Deploy service
When you install and deploy the service EAR file, check carefully any messages given when the service is deployed.
Server setup and start
Make sure that the WebSphere Application Server server.policy file (in the /properties directory) has the correct security settings. For more information, see Enabling security for WSIF.
WSIF setup
Check that the wsif.properties file is correctly set up. For more information, see Maintaining the WSIF properties file.
Run client
Either check that you have defined the class path correctly to include references to your client classes, WSIF JAR files and any other necessary JAR files, or (preferably) run your client using the WebSphere Application Server launchClient tool.

Here is a list of common errors, and information on their probable causes:

Steps for this task (dependent on configuration)




Sub-topics
Trace and logging for WSIF
WSIF (Web Services Invocation Framework) messages
WSIF - Known restrictions

Related tasks
Maintaining the WSIF properties file
Enabling security for WSIF
WSIF system management and administration

Task topic    

Terms of Use | Feedback

Last updated: Jun 8, 2005 12:45:23 PM EDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/twsf_trouble.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)