Troubleshooting WSIF

Use this overview task to help resolve a problem that you think is related to the Web Services Invocation Framework (WSIF).

This topic references one or more of the application server log files. As a recommended alternative, we can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM i systems. We can also use HPEL in conjunction with the native z/OS logging facilities. If we are using HPEL, we can access all of the log and trace information using the LogViewer command-line tool from the server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

For information about resolving WebSphere Application Server-level problems, see Diagnosing problems (using diagnosis tools).

To identify and resolve WSIF-related problems, we can use the standard WebSphere Application Server 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 administrative console, and in the application server stdout.log file. We can also enable the application server 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.

1. 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. For more information, see Tracing and logging WSIF.

2. 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 application server SystemOut log at was_home\logs\server\SystemOut.

   Check in the SYSPRINT or SYSOUT log.

3. 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.

4. Check the set of specific tips to help troubleshoot problems you experience with WSIF.

   For more information, see Web Services Invocation Framework troubleshooting tips.

5. Check the list of the main known restrictions that apply when using WSIF.

   For more information, see WSIF - Known restrictions.

Subtopics

• Tracing and logging WSIF
  The Web Services Invocation Framework (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.

• WSIF (Web Services Invocation Framework) messages
  WebSphere system messages are logged from a variety of sources, including application server components and applications. Messages logged by application server components and associated IBM products start with a unique message identifier that indicates the component or application that issued the message. Here is a list of the WSIF runtime system messages, with details of what each message means.

• Web Services Invocation Framework troubleshooting tips
  A set of specific tips to help troubleshoot problems you experience with the Web Services Invocation Framework (WSIF).

• WSIF - Known restrictions
  The known restrictions that apply when using WSIF include restrictions on threading, on SOAP headers and unreferenced attachments, and on data type mappings.

Related tasks

Use High Performance Extensible Logging to troubleshoot applications