Troubleshooting WSIF

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

Before you begin

Note: This topic references one or more of the application server log files. As a recommended alternative, you 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. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your 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).

About this task

To identify and resolve 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.

The documentation also includes details of common WSIF-related problems, specific WSIF troubleshooting tips and known WSIF restrictions.

Procedure

  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 you are using WSIF outside of WebSphere Application Server. 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.

    [AIX Solaris HP-UX Linux Windows][IBM i]Check in the application server SystemOut log at was_home\logs\server\SystemOut.

    [z/OS]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 you 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.


Icon that indicates the type of topic Task topic



Timestamp icon Last updated: March 5, 2017 17:29
File name: twsf_trouble.html