InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.0: About user assistance >
6.6.0.2: Command line administration >
6.6.0.2.2: WebSphere Control Program (wscp) >
6.6.0.2.2.3: Advanced usage of wscp >
6.6.0.2.2.3.8: Enabling tracing with DrAdmin

6.6.0.2.2.3.8: Enabling tracing with DrAdmin

In addition to the EjscpExtension class, WebSphere Advanced Application Server includes the wscp DrAdmin operations for tracing. The DrAdmin operations can be used to trace an administrative server or any application server in a domain.

  • The DrAdmin local operation traces the wscp client itself.

  • The DrAdmin remote operation traces the administrative server or an application server (the server can be local, running on the same machine as wscp, or it can be running on a remote machine).

The syntax for both commands is as follows:

DrAdmin local  [-setTrace trace_spec] [-setRingBufferSize size]
[-dumpRingBuffer file_name] [-dumpState file_name]
DrAdmin remote  server_port [-serverHost host_name [-setTrace trace_spec]
[-dumpRingBuffer file_name] [-dumpState file_name
[-setRingBufferSize string] [-stopServer] [-stopNode] [-dumpThreads]

The arguments and options are as follows:

  • server port. A port number is displayed as an Audit message in the Console Messages window when each server starts and when the administrative server starts. These audit messages are written to the file named tracefile in the logs subdirectory of the WebSphere home installation directory.

  • -serverHost. Specifies the name of the machine where the administrative server or application server is running.

  • -setTrace. Specifies a trace specification.

  • -setRingBufferSize. Specifies the size of the ring buffer in kilobytes. The default is 8 KB.

  • -dumpRingBuffer. Specifies a file name where the ring buffer is to be written. By default, the ring buffer is written to the current working directory. If the administrative server is started as a Windows NT service, the ring buffer is written to the system default directory C:\WINNT\system32.

  • -dumpState. Specifies a file name where state information for the server is to be written.

  • -stopServer. Stops the server being traced.

  • -stopNode. Stops the node.

  • -dumpThreads. Specifies a file name where thread history and error information is to be written.

In the following example, the DrAdmin extension is used to trace the administrative server running on port 1078. By default, the trace ring buffer is written to the system default directory. The second example specifies a file name where the trace is to be written. (For Windows NT pathnames, you can use forward slashes (/). If backslashes are used, they must be prefaced with the backslash (\) character so that the backslashes are treated as ordinary characters.) The third example sets a trace specification that enables tracing for all container classes.

wscp> DrAdmin remote 1078
Server trace ring buffer dumped into file JmonDump52701921622
wscp> DrAdmin remote 1078 -dumpRingBuffer e:\\wscp\\dradmin.dump
Server trace ring buffer dumped into file e:\wscp\dradmin.dump
wscp> DrAdmin remote 1078 -setTrace com.ibm.ejs.container.*=all=enabled
Server trace set to com.ibm.ejs.container.*=all=enabled
Server trace ring buffer dumped into file e:\wscp\dradmin.dump
Go to previous article: 6.6.0.2.2.3.7: Tracing the administrative server, application servers, and the wscp client Go to next article: 6.6.0.2.2.3.9: Manipulating the JNDI context of objects

 

 
Go to previous article: 6.6.0.2.2.3.7: Tracing the administrative server, application servers, and the wscp client Go to next article: 6.6.0.2.2.3.9: Manipulating the JNDI context of objects