InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.19: Administering the product messages, logs, and traces (overview) >
6.6.19.3: Administering server traces with the Web console

6.6.19.3: Administering server traces with the Web console

Use the Web console to trace components of the application server runtime. You can learn more about the tracing tool, DrAdmin, in the problem determination section of the IBM WebSphere Application Server documentation (see the InfoCenter).

(If you are looking for information about tracing and debugging applications being hosted by the application server, see these topics instead: instructions for starting application servers and configuring Distributed Debugger and OLT support).

There are two basic scenarios for using the trace settings:

  • Configuration changes. Like the majority of settings available in the Web console, you can change trace settings and save them to the server configuration file. They will take effect the next time you start the server.
  • Runtime tasks. You can perform tasks against the trace service that is part of a running application server. For example, you can initiate a trace of specific components by sending a trace string to the running application server. These tasks yield immediate results. Saving the changes to the server configuration file so that they take effect the next time the server is started is optional.

Work with the trace service by locating it in the tree on the left side of the console:

Nodes -> hostname -> Application Servers -> Trace Service

There is also a related set of properties for defining Standard Error and Standard Out streams:

Nodes -> hostname -> Application Servers -> IO Redirect

Go to previous article: Server trace properties Go to next article: Enabling and specifying trace strings with the Web console

 

 
Go to previous article: Server trace properties Go to next article: Enabling and specifying trace strings with the Web console