bea.com | products | dev2dev | support | askBEA

Download Docs | Site Map | Glossary
Search

Administration Console Online Help

Domain --> Configuration --> Logging

Tasks Additional Documentation Attributes

Overview

The Domain—>Configuration—>Logging tab configures the location, file-rotation criteria, and number of files that the Administration Server uses to store domain log messages.

The domain's log contains messages that individual servers within the domain have forwarded. By default, only the log messages of an ERROR or higher severity are forwarded from the local servers to the domain log. To change the default, you must create a domain log filter.

The file-rotation criteria determine when the Administration Server moves old messages to another file.

Tasks

Viewing the Domain Log

Specifying Criteria for Rotating Domain Log Files

Creating a New Domain Log Filter

Viewing Server Logs

Additional Documentation

(Requires an Internet connection.)

Using Log Messages to Manage WebLogic Servers

Attributes

Attribute Label | Description | Value Constraints
--- | --- | ---
File Name | The name of the file that stores current log messages. 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. If the name does not include a path element, then pathname will be computed as follows: For a server log file, ./SERVER_NAME For a domain log file, ./ If neither file name nor pathname is specified, then the name is computed as follows: For a server log file, ./SERVER_NAME/SERVER_NAME.log For a domain log file, ./DOMAIN_NAME.log 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, weblogic_%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.LogMBean Attribute: FileName | Default: "weblogic.log" Configurable: yes Readable: yes Writable: yes
Rotation Type | Criteria for moving old log messages to a separate file: NONE. Messages accumulate in a single file. You must erase the contents of the file when the size is unwieldy. SIZE. When the log file reaches the size that you specify in FileMinSize, the server renames the file. TIME. At each time interval that you specify in TimeSpan, 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 FileName. MBean: weblogic.management. configuration.LogMBean Attribute: RotationType | Default: "none" Valid values: "bySize" "byTime" "none" Configurable: yes Dynamic: yes Readable: yes Writable: yes
File Min Size | 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 minimum 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. MBean: weblogic.management. configuration.LogMBean Attribute: FileMinSize | Units: kilobytes Minimum: 1 Maximum: 65535 Default: 500 Configurable: yes Dynamic: 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 FileTimeSpan. Use the following format: hh:mm, where hh is the hour in a 24-hour format and mm is the minute. If the time that you specify has already past, then the server starts its file rotation immediately. MBean: weblogic.management. configuration.LogMBean Attribute: RotationTime | Default: 00:00 Configurable: yes Dynamic: yes Readable: yes Writable: yes
File Time Span | The interval (in hours) at which the server saves old log messages to another file. This value is relevant only if you use the time-based rotation type. MBean: weblogic.management. configuration.LogMBean Attribute: FileTimeSpan | Units: hours Minimum: 1 Default: 24 Configurable: yes Dynamic: yes Readable: yes Writable: yes
Number Of Files Limited | Limits the number of files that a server creates to store old messages to the maximum number specified in FileCount. After the server reaches this limit, it overwrites the oldest file. If you do not enable this option, the server creates new files indefinitely. You must clean up these files as you require. This value is relevant only if you specify a file rotation type of SIZE or TIME. MBean: weblogic.management. configuration.LogMBean Attribute: NumberOfFilesLimited | Default: false Dynamic: yes Readable: yes Writable: yes
File Count | The maximum number of log files that the server creates when it rotates the log. Only valid if isNumberOfFilesLimited is true and setRotationType is either Size or Time. MBean: weblogic.management. configuration.LogMBean Attribute: FileCount | Default: 7 Configurable: yes Dynamic: yes Readable: yes Writable: yes