Enabling trace on a running server

Use the administrative console to enable tracing on a running server. You can use trace to assist you in monitoring system performance and diagnosing problems.

About this task

You can modify the trace service state that determines which components are being actively traced for a running server by using the following procedure.

[z/OS]You can also configure tracing from the MVS™ console using the modify command.

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

Procedure

  1. Start the administrative console.
  2. [AIX Solaris HP-UX Linux Windows][IBM i]Click Troubleshooting > Logs and Trace in the console navigation tree, then click server > Diagnostic Trace.
  3. Select the Runtime tab.
  4. Select the Save runtime changes to configuration as well check box if you want to write your changes back to the server configuration.
  5. Change the existing trace state by changing the trace specification to the desired state. Refer to the following topics for specific information on how to change your trace specifications:
    • "Diagnostic trace service settings" describes how you can examine the current diagnostic trace settings and to change where the trace is written (memory buffer or file). If the trace is to be recorded in a memory buffer, you can specify the file to which the memory buffer is to be dumped. You can view the file for trace information.
    • "Log and trace settings" describes how you can view and configure logging and trace settings for the server.
    • "Managing the application server trace service" describes how you can manage the trace service for a server process while the server is stopped and while it is running. You can specify which components to trace, where to send trace output, the characteristics of the trace output device, and which format to generate trace output in. You can select where the trace is written (memory buffer or file).
    避免困難 避免困難: The clauses included in a trace specification are read in the order they appear in the string. Therefore, if multiple variations of the *=info clause are included in a trace specification, the last value specified is the value that determines the trace level that the system logs. If you specify *=info as the last clause, tracing occurs at the info level regardless of other clauses that are specified in the trace string. For example, if you specified the following trace string:
    *=info:PMGR=all:*=info:com.ibm.ws.sm.*=all
    is equivalent to simply specifying:
    *=all
    Because the final clause overrides all clauses that were specified ahead of it in the string.gotcha

    On an application server, trace output can be directed either to a file or to an in-memory circular buffer. If trace output is directed to the in-memory circular buffer, it must be dumped to a file before it can be viewed.

    On an application client or stand-alone process, trace output can be directed either to a file or to the process console window.

  6. Configure the trace output if a change from the existing one is desired.
  7. Click Apply.

指出主題類型的圖示 作業主題



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