Technical data

7 Configuring WebLogic Server Web Components
7-14 Configuring and Managing WebLogic Server
Setting Up HTTP Access Logs
WebLogic Server can keep a log of all HTTP transactions in a text file, in either
common log format or extended log format. Common log format is the default, and
follows a standard convention. Extended log format allows you to customize the
information that is recorded. You can set the attributes that define the behavior of
HTTP access logs for each server or for each virtual host that you define.
For information on setting up HTTP logging for a server or a virtual host, refer to the
following topics in the Administration Console online help:
! Specifying HTTP Log File Settings for a Server
! Specifying HTTP Log File Settings for a Virtual Host
Log Rotation
You can also choose to rotate the log file based on either the size of the file or after a
specified amount of time has passed. When either one of these two criteria are met, the
current access log file is closed and a new access log file is started. If you do not
configure log rotation, the HTTP access log file grows indefinitely. The name of the
access log file includes a numeric portion that is incremented upon each rotation.
Separate HTTP Access logs are kept for each Web Server you have defined.
Common Log Format
The default format for logged HTTP information is the common log format at
http://www.w3.org/Daemon/User/Config/Logging.html#common-logfile-
format
. This standard format follows the pattern:
host RFC931 auth_user [day/month/year:hour:minute:second
UTC_offset] "request" status bytes
where:
host
Either the DNS name or the IP number of the remote client