IBM E02HRLL-G - WebSphere Partner Gateway Express, Руководство администратора

Страница: 147 / 268

For both modes, the steps to configure the circular log files used by a server are
the same.
1.
Locate the server in the console by clicking on Servers/Application servers in
the left pane to list the server names in the right pane.
2. View the details of the server that you want to configure by selecting the server
name in the list.
3. Scroll down until you see the Troubleshooting heading near the bottom of the
page. Click Logging and Tracing under Troubleshooting .
4. Click JVM logs to see the details of the logging configuration.
5. The tabbed window that displays contains a tab called Configuration and one
called Runtime .
Note:
a.
Changes made on the Configuration page take effect after the server is
restarted. These changes persist across server restarts.
b. Changes on the Runtime page take effect immediately but do not persist
across server restarts unless Save runtime changes to the master
configuration is selected.
Key features of the Configuration page are that:
v You are presented two sections on the page, one to configure for standard
output logging and the other to configure standard error logging.
v
You can change the name and the path to the files that are used to store the
log messages for the server.
v
You can change the format used for the log messages. Both of the formats
provide the message that the application writes. The difference between the
basic and advanced formats is how much
meta-information is provided with
each message. Meta-information is information such as the time the log was
written (basic and advanced) and the name of the thread (advanced only)
that wrote the information.
v You can control how the circular logging is configured. Options are provided
to set the size, number of files in the ring, and rollover triggering method
(file size or time).
The key feature of the Runtime page is that you can view the log files by
clicking View for a specific file. The line numbers that are displayed can be
changed by entering a range of line numbers and refreshing the viewer page.
For a complete description of these features, see the WebSphere Application Server
documentation.
Trace file management
Managing trace files includes:
v Controlling the amount of disk space that trace files can consume
v
Setting the names and paths for the trace files
v Setting the trace file format
v
Determining which WebSphere Partner Gateway components write trace
information to the files
v
Setting the trace level for the selected components.
You set the trace configuration using the WebSphere Application Server admin
console.
Chapter 14. Using logging and tracing features
141