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 WebSphere Application Server.

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .

To enable trace and logging for WSIF, complete either or both of the following steps:

Tasks

• Enable trace for the WSIF API within WAS, and have trace, stdout and stderr for the application server written to a well-known location.

  To trace the WSIF API, specify the following trace string:

  wsif=all=enabled
  

  (ZOS) See Set up component trace (CTRACE).

• Enable the WSIF SimpleLog utility, through which we can run trace when we are using WSIF outside of WAS.

  1. Create a file named commons-logging.properties with the following contents:

     org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
     org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
     

  2. Create a file named simplelog.properties with the following contents:

     org.apache.commons.logging.simplelog.defaultlog=trace
     org.apache.commons.logging.simplelog.showShortLogname=true
     org.apache.commons.logging.simplelog.showdatetime=true
     

  3. Put both these files, and the commons-logging.jar file, on the class path.

  The SimpleLog utility writes trace to the System.err file.

Use High Performance Extensible Logging to troubleshoot applications

WSIF (Web Services Invocation Framework) messages