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 시스템에서 SystemOut.log, SystemErr.log, trace.logactivity.log 파일을 사용하는 대신 HPEL(High Performance Extensible Logging) 로그를 사용하고 인프라를 추적하도록 서버를 구성하는 것입니다. 원시 z/OS® 로깅 기능과 연계하여 HPEL을 사용할 수도 있습니다. HPEL을 사용하는 경우 서버 프로파일 바이너리 디렉토리의 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 6:13
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=ttrb_entrrs
파일 이름:ttrb_entrrs.html