Trace user interface for stand-alone clients

To enable trace, you can either use a long form or a short form system property.

Note: 這個主題參照一或多個應用程式伺服器日誌檔。 此外,在分散式和 IBM® i 系統上,另外也建議您可以配置伺服器來使用「高效能可延伸記載 (HPEL)」日誌和追蹤基礎架構,而不使用 SystemOut.logSystemErr.log, trace.logactivity.log 檔案。HPEL 與原生 z/OS® 記載機能也可以一起使用。如果您使用 HPEL,則可以從伺服器設定檔 bin 目錄,利用 LogViewer 指令行工具來存取您所有的日誌和追蹤資訊。請參閱有關利用 HPEL 疑難排解應用程式的資訊,以取得更多使用 HPEL 的相關資訊。

Long form system properties

The long form system property takes priority over the short form and uses system properties that are unique to WebSphere® Application Server.

Table 1. Long form system properties. The table contains the list of long form system properties and the descriptions of the properties.
Property Description
com.ibm.ejs.ras.lite.traceSpecification The trace specification string
com.ibm.ejs.ras.lite.traceFileName The trace destination (<file>, stdout, stderr, java,util.logging)
com.ibm.ejs.ras.lite.maxFileSize The maximum trace file size in MB (if the trace destination is a file)
com.ibm.ejs.ras.lite.maxFiles The maximum number of trace files kept (if the trace destination is a file)
com.ibm.ejs.ras.lite.traceFormat The trace output format, which can be either basic or advanced (the default is basic)

Long form example:

-Dcom.ibm.ejs.ras.lite.traceSpecification=SIB*=all
-Dcom.ibm.ejs.ras.lite.traceFileName=c:/trace.log
-Dcom.ibm.ejs.ras.lite.maxFileSize=20
-Dcom.ibm.ejs.ras.lite.maxFiles=8

Short form system property

The short form uses a system property that is compatible with existing WebSphere Application Server clients but that, because this property is unqualified, might clash with other third party technologies that are running in the same Java™ runtime environment (JRE).

The short form system property is:

traceSettingsFile
This property must specify a loadable properties file that can contain the following properties:
Table 2. Properties in loadable system properties file. The table includes the list of loadable system properties and the descriptions of the properties.
Property Description
traceFileName The trace destination (file, stdout, stderr, java,util.logging)
maxFilesSize The maximum trace file size in MB (if the trace destination is a file)
maxFiles The maximum number of trace files kept (if the trace destination is a file)
<traceSpec> The trace specification
traceFormat The trace output format, which can be either basic or advanced (the default is basic)

The following example shows how to use the short form system property:

SIBTrm=all:SIBMfp=all
traceFileName=c:/trace.log

Special meanings for trace file name values

Some trace file name values have a special meaning:
  • stdout - causes trace records to be written to stdout
  • stderr - causes trace records to be written to stderr
  • java.util.logging - causes trace records to be written to java.util.logging

Using any other name causes the trace records to be written to a file of that name.


指出主題類型的圖示 概念主題



時間戳記圖示 前次更新: July 9, 2016 11:10
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=cjj_stdalonecli_trace
檔名:cjj_stdalonecli_trace.html