bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Server --> Logging --> HTTP

Tasks Additional Documentation Attributes

Overview

The Server—>Logging—>HTTP tab configures HTTP logging for the server. If you enable HTTP logging, the server saves HTTP requests in a separate log file; it does not store HTTP requests in the server log file or the domain log file.

You can also specify the name of the log file that stores HTTP requests and the longevity and format of the data in the file.

Note: If you set up HTTP logging for a virtual host, all HTTP requests for the virtual host are saved in a separate log file.

Tasks

Specifying HTTP Log File Settings for a Server

Additional Documentation

(Requires an Internet connection.)

For more information about log files, please see the following topics:

- Setting Up HTTP Access Logs in the Administration Guide. This topic includes information about using the extended format in HTTP logs.

- Using Log Messages to Manage WebLogic Servers in the WebLogic Server Administration Guide

For information about VirtualHosts, please see "Configuring Virtual Hosting" under Configuring WebLogic Server Web Components in the Administration Guide.

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
Enable Logging | Enables logging of HTTP requests. MBean: weblogic.management. configuration. WebServerMBean Attribute: LoggingEnabled | Default: true Readable: yes Writable: yes
Logfile Name | The name of the file that stores HTTP requests. If the pathname is not absolute, the path is assumed to be relative to the root directory of the machine on which the server is running. This value is relevant only if HTTP logging is enabled. To include a time or date stamp in the file name when the log file is rotated, add java.text.SimpleDateFormat variables. Surround each variable with percentage (%) characters. For example, access_%yyyy%_%MM%_%dd%_%hh%_%mm%.log If you do not include a time and date stamp, the rotated log files are numbered in order of creation filename nnnnn, where filename is the name configured for the log file. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogFileName | Default: "access.log" Configurable: yes Readable: yes Writable: yes
Format | Specifies the format of the HTTP log file. Both formats are defined by the W3C. With the extended log format, you use server directives in the log file to customize the information that the server records. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogFileFormat | Default: "common" Valid values: "common" "extended" Configurable: yes Dynamic: yes Readable: yes Writable: yes
Log Time In GMT | Writes the time stamp of HTTP log messages in Greenwich Mean Time (GMT) regardless of whether the host computer has specified a different local time zone. Use this feature to comply with the W3C specification for Extended Format Log Files. This specification states that all time stamps for Extended Format log entries should be in GMT: http://www.w3.org/TR/WD-logfile.html. This attribute applies only if you have specified the extended message format. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogTimeInGMT | Default: "false" Configurable: yes
Log Buffer Size | The maximum size (in kilobytes) of the buffer that stores HTTP requests. When the buffer reaches this size, the server writes the data to the HTTP log file. Use the LogFileFlushSecsproperty to determine the frequency with which the server checks the size of the buffer. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogFileBufferKBytes | Units: kilobytes Minimum: 0 Maximum: 1024 Default: 8 Readable: yes Writable: yes
Max Log File SizeK Bytes | The file size (1 - 65535 kilobytes) that triggers the server to move log messages to a separate file. After the log file reaches the specified size, the next time the server checks the file size, it will rename the current log file and create a new one to store subsequent messages. 0 causes the file to grow indefinitely. This property is relevant only if you choose to rotate files by size. MBean: weblogic.management. configuration. WebServerMBean Attribute: MaxLogFileSizeKBytes | Units: kilobytes Minimum: 0 Default: 0 Configurable: yes Readable: yes Writable: yes
Rotation Type | Criteria for moving old HTTP requests to a separate log file: size. When the log file reaches the size that you specify in MaxLogFileSizeKBytes, the server renames the file. date. At each time interval that you specify in LogRotationPeriodMin, the server renames the file. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in LogFileName. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogRotationType | Default: "size" Valid values: "size" "date" Configurable: yes Readable: yes Writable: yes
Rotation Period | The interval (in minutes) at which the server saves old HTTP requests to another log file. This value is relevant only if you use the date-based rotation type. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogRotationPeriodMins | Units: minutes Minimum: 1 Maximum: 2147483647 Default: 1440 Configurable: yes Readable: yes Writable: yes
Flush Every | The interval (in seconds) at which the server checks the size of the buffer that stores HTTP requests. When the buffer exceeds the size that is specified in the LogFileBufferKBytesproperty, the server writes the data in the buffer to the HTTP request log file. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogFileFlushSecs | Units: seconds Minimum: 1 Maximum: 360 Default: 60 Configurable: yes Readable: yes Writable: yes
Rotation Time | Determines the start time for a time-based rotation sequence. At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in LogRotationPeriodMins. Use the following java.text.SimpleDateFormat format to specify a date and time: MM-dd-yyyy-k:mm:ss. For information about this format, refer to the J2EE Javadoc. If the time that you specify has already past, then the server starts its file rotation immediately. MBean: weblogic.management. configuration. WebServerMBean Attribute: LogRotationTimeBegin | Configurable: yes Readable: yes Writable: yes