IBM E02HRLL-G Administration Guide - Page 145
Using logging and tracing features, Log and trace files
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 145 highlights
Chapter 14. Using logging and tracing features One of the tasks of the WebSphere Partner Gateway administrator is to help diagnose problems that arise when documents are being processed. Logging and tracing are the tools that are used in the diagnosis of the problems. The administrator needs to know how to configure the system so it can provide the information needed to diagnose problems. WebSphere Application Server provides sophisticated logging and tracing capabilities that are available to applications that it hosts. WebSphere Partner Gateway components are applications that are hosted by WebSphere Application Server, and they use the WebSphere log and trace capabilities. WebSphere Application Server documentation contains general information about configuring logging and tracing, but in order to use it for WebSphere Partner Gateway, there are many specific things that you need to know. In this chapter, you will find a summary of the important items you need to know about using the WebSphere Application Server console to control logging and tracing. In addition to this general information, you will also find the specific items about using logging and tracing to solve WebSphere Partner Gateway problems. Log and trace files The log and trace files used for WebSphere Partner Gateway are described in this section: SystemOut.log and SystemErr.log Log messages are written whenever an application writes to the standard output stream or standard error stream. Application developers can write messages to these streams to provide general information about the status of the programs. For example, when an application is starting up, log messages are often provided to verify that the subsystems used by the application have been accessed, and that the application itself has started. When Exceptions occur, these are recorded in the form of a log message by the application that detected the Exception. The stack trace showing the state of the system when an Exception occurred is saved by writing it to the standard error stream. Log messages are written to the following WebSphere Application Server files: v SystemOut.log which records messages written to the standard output stream. v SystemErr.log which records messages written to the standard error stream. There is not a way to filter log messages so that only some are written and others are omitted. Since they are always written, log messages tend to be short and general in nature. Often they are useful because they do provide information about the status of the system and they can give you hints about what kind of detailed tracing you should use when a problem occurs. Trace file Unlike log messages, trace messages are only written by applications when © Copyright IBM Corp. 2007, 2008 139