Troubleshooting WSIF
Use this overview task to help resolve a problem that you think is related to the Web Services Invocation Framework (WSIF).
For information about resolving WAS-level problems, see Diagnose problems (using diagnosis tools).
To identify and resolve WSIF-related problems, we can use the standard WAS trace and logging facilities. If we encounter a problem that you think might be related to WSIF, we can check for error messages in the WAS admin console, and in the appserver stdout.log file. We can also enable the appserver debug trace to provide a detailed exception dump.
The documentation also includes details of common WSIF-related problems, specific WSIF troubleshooting tips and known WSIF restrictions.
- Trace and log WSIF.
WSIF offers trace points at the opening and closing of ports, the invocation of services, and the responses from services. WSIF also includes a SimpleLog utility that can run trace when we are using WSIF outside of WAS.
- Check for error messages about WSIF.
A list of the WSIF runtime system messages, with details of what each message means, is provided in WSIF (Web Services Invocation Framework) messages.
Check in the appserver's SystemOut log at was_home\logs\server\SystemOut.
- Check the list of major WSIF activities, with advice on common problems associated with each activity
For more information, see Web Services Invocation Framework troubleshooting tips.
- Check the set of specific tips to help you troubleshoot problems you experience with WSIF.
- Check the list of the main known restrictions that apply when using WSIF.
Tracing and logging WSIF
WSIF (Web Services Invocation Framework) messages
Web Services Invocation Framework troubleshooting tips
WSIF - Known restrictions
Related tasks
Manage WSIF