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 you are using WSIF outside of WebSphere® Application
Server.
Before you begin
Note: 這個主題參照一或多個應用程式伺服器日誌檔。
此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.log、SystemErr.log, trace.log 及 activity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。
About this task
To enable trace and logging for WSIF, complete either
or both of the following steps:
Procedure
- Enable trace for the WSIF API within WebSphere Application
Server, 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
- Enable the WSIF SimpleLog utility, through
which you can run trace when you are using WSIF outside of WebSphere Application Server.
- 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
- 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
- Put both these files, and the commons-logging.jar file,
on the class path.
The SimpleLog utility writes trace to
the System.err file.