[AIX Solaris HP-UX Linux Windows][IBM i]

Diagnostic trace service settings

Use this page to configure diagnostic trace service settings.

支援的配置 支援的配置: You can only access this page when the server is configured to use basic log and trace mode.sptcfg

To view this administrative console page, click Troubleshooting > Logs and trace > server_name > Diagnostic trace.

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

Trace Output

Specifies where trace output should be written. The trace output can be written directly to an output file, or stored in memory and written to a file on demand using the Dump button found on the runtime page.

Different components can produce different amounts of trace output per entry. Naming and security tracing, for example, produces a much higher trace output than web container tracing. Consider the type of data being collected when you configure your memory allocation and output settings.

None
If this option is selected, the trace data is not logged or recorded anywhere. All other handlers (including handlers registered by applications) still have an opportunity to process these traces.
Memory Buffer
Specifies that the trace output should be written to an in-memory circular buffer. If you select this option you must specify the following parameters:
Maximum Buffer Size
Specifies the number of entries, in thousands, that can be cached in the buffer. When this number is exceeded, older entries are overwritten by new entries.
File
Specifies to write the trace output to a self-managing log file. The self-managing log file writes messages to the file until the specified maximum file size is reached. When the file reaches the specified size, logging is temporarily suspended and the log file is closed and renamed. The new name is based on the original name of the file, plus a timestamp qualifier that indicates when the renaming occurred. Once the renaming is complete, a new, empty log file with the original name is reopened, and logging resumes. No messages are lost as a result of the rollover, although a single message may be split across the two files. If you select this option you must specify the following parameters:
Maximum File Size
Specifies the maximum size, in megabytes, to which the output file is allowed to grow. This attribute is only valid if the File Size attribute is selected. When the file reaches this size, it is rolled over as previously described.
Maximum Number of Historical Files
Specifies the maximum number of rolled over files to keep.
File Name
Specifies the name of the file to which the trace output is written.
避免困難 避免困難: This file cannot be shared between servers. The server creates a file with a .owner extension to help detect when two or more servers happen to be trying to use the same file.gotcha

Trace Output Format

Specifies the format of the trace output.

You can specify one of three levels for trace output:
Basic (Compatible)
Preserves only basic trace information. Select this option to minimize the amount of space taken up by the trace output.
Advanced
Preserves more specific trace information. Select this option to see detailed trace information for use in troubleshooting and problem determination.
Log analyzer trace format
Preserves trace information in the same format as produced by Showlog tool.

Runtime tab

Save runtime changes to configuration

Save runtime changes made on the runtime tab to the trace configuration as well. Select this box to copy runtime trace changes to the trace configuration settings as well. Saving these changes to the trace configuration will cause the changes to persist even if the application is restarted.

Trace Output

Specifies where trace output should be written. The trace output can be written directly to an output file, or stored in memory and written to a file on demand using the Dump button found on the run-time page.

None
If this option is selected, the trace data is not logged or recorded anywhere. All other handlers (including handlers registered by applications) still have an opportunity to process these traces.
Memory Buffer
Specifies that the trace output should be written to an in-memory circular buffer. If you select this option you must specify the following parameters:
Maximum Buffer Size
Specifies the number of entries, in thousands, that can be cached in the buffer. When this number is exceeded, older entries are overwritten by new entries.
Dump File Name
The name of the file to which the memory buffer will be written when it is dumped. This option is only available from the Runtime tab.
File
Specifies to write the trace output to a self-managing log file. The self-managing log file writes messages to the file until the specified maximum file size is reached. When the file reaches the specified size, logging is temporarily suspended and the log file is closed and renamed. The new name is based on the original name of the file, plus a timestamp qualifier that indicates when the renaming occurred. Once the renaming is complete, a new, empty log file with the original name is reopened, and logging resumes. No messages are lost as a result of the rollover, although a single message may be split across the two files. If you select this option you must specify the following parameters:
Maximum File Size
Specifies the maximum size, in megabytes, to which the output file is allowed to grow. This attribute is only valid if the File Size attribute is selected. When the file reaches this size, it is rolled over as previously described.
Maximum Number of Historical Files
Specifies the maximum number of rolled over files to keep.
File Name
Specifies the name of the file to which the trace output is written.
View
View the file that is specified by the File Name parameter. This does not apply your configuration.
避免困難 避免困難: Do not specify the same file name for more than one managed server. The server creates a file with a .owner extension to track which server can use a particular file name for output.gotcha

指出主題類型的圖示 參照主題



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