e-docs > WebLogic Server > Administration Console Online Help > Virtual Hosts |
Administration Console Online Help |
Virtual Host --> Configuration --> Logging
Tasks Additional Documentation Attributes
The Virtual Host
You can also use this tab to specify the longevity and format of the data in the virtual hosts's HTTP log file.
Specifying HTTP Log File Settings for a Virtual Host
(Requires an Internet connection.)
For more information about HTTP logs, see "Setting Up HTTP Access Logs" under Configuring WebLogic Server Web Components in the Administration Guide. This topic includes information about using the extended format in HTTP logs.
For more information about VirtualHosts, please see the Administration Guide, Configuring WebLogic Server Web Components.
Enables logging of HTTP requests. |
||
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 filenamennnnn, where filename is the name configured for the log file. |
||
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. |
||
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. |
||
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. |
||
Criteria for moving old HTTP requests to a separate log file:
After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in LogFileName. |
||
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. |
||
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. |
||
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. |