IBM E02HRLL-G Administration Guide - Page 150
Setting log detail levels, Trace Output, memory buffer, Runtime, trace file, trace output format
![]() |
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 150 highlights
v Trace messages can be written to a memory buffer or to a file. You specify this by choosing one of the Trace Output radio buttons. - If you select the memory buffer option, you must have a way to take what is in memory and put it into a file so you can see the messages. This is done from the Runtime page, and is discussed later in this section. - If you use the trace file option, you configure a circular log similar to the way the system circular logging is configured. By using circular logging, you can limit the growth of the trace files so they do not consume too much of your file system resource. You can also configure the path and file name for the trace files. - The trace output format option can either be Basic or Advanced. Trace files can also be written using a binary format called the Log Analyzer format. By specifying the log analyzer format, you can open a trace output file using the Log Analyzer tool. The Log Analyzer tool is an application included with the WebSphere Application Server. See the WebSphere Application Server documentation for more information about the Log Analyzer. The key benefit of the Runtime page is that you can dynamically change the trace logging without restarting the server. You can reflect any changes that you make at runtime into the persistent configuration if you select Save runtime changes to configuration before saving. For a complete description of these features, see the WebSphere Application Server documentation. Setting log detail levels When problems occur, services and support personnel may ask for trace files to help understand the nature of the problem. As the administrator of the system, you will configure the system to obtain the tracing that is useful for diagnosing problems. That is the purpose of setting the logging levels. When you set the logging level for a server: v You determine which WebSphere Partner Gateway components (Java classes) write trace messages. v You determine the types of messages that are included in the trace file using an importance scale with five levels. Trace messages are classified using severity levels that are derived from levels used by WebSphere Partner Gateway version 6.0 and earlier. These old severity levels are mapped to WebSphere Application Server severity levels according to Table 41. This table illustrates how to use the new levels to achieve the same level of trace. Table 41. WebSphere Application Server severity levels Version 6.1 severity level Version 6.2 severity level FATAL FATAL ERROR SEVERE WARN WARNING INFO INFO DEBUG FINEST Log detail levels are accessed using a link that is provided on the Diagnostic tracing Configuration and Runtime pages for an application server. When you click this link, you are presented with a page that shows a tree-view of 144 IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
![](/manual_guide/products/ibm-e02hrllg-administration-guide-f948001/150.png)