Oracle Fusion Middleware Documentation > Oracle WebLogic Server 12.1.3.0 Documentation > Administration Console Online Help > Enable and configure Datasource Profile logs

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Enable and configure Datasource Profile logs


By default, the DataSource subsystem optionally keeps a log of all DataSource profile information in a text file. The default location and rotation policy for DataSource Profile logs is the same as the server log, in the logs directory below the server instance root directory. See Change server log file name and location.

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left pane of the Console, expand Environment and select Servers.
  3. In the Servers table, click the name of the server instance whose DataSource Profile logging you want to configure.
  4. Select Logging > DataSource.
  5. On the Logging: DataSource page:
    1. In the Log File Name field, enter a path and filename for the DataSource Profile log.

      Enter an absolute pathname or a pathname that is relative to the server's root directory. If you use the Node Manager to start a Managed Server, the root directory is located on the computer that hosts the Node Manager process. For more information, see A Server's Root Directory.

    2. To include a time and date stamp in the file name when the log file is rotated, in the Log File Name field, add java.text.SimpleDateFormat variables to the file name and surround each variable with percentage (%) characters.
  6. By default, the server moves old DataSource profile records to another file when the current DataSource Profile log file grows beyond 5000 kilobytes when running a WebLogic Server instance in production mode, or 500 kilobytes when running a WebLogic Server instance in development mode. Also by default, the server can create an unlimited number of these archive log files. To change these defaults:
    1. In the Rotation File Size field, enter the file size that triggers the server to move DataSource profile records to a separate file. After the DataSource Profile log file reaches the specified size, the next time the server checks the file size, it will rename the current log file. After the server renames a file, subsequent messages accumulate in a new file named access.log.
    2. To limit the number of DataSource Profile log files that the server creates to store old DataSource profile records, select the Limit Number of Retained Files check box. Then in the Files to Retain field, enter the maximum number of log files. After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.
  7. To move old DataSource profile records to another file at specific time intervals instead of when the log file reaches a specific size:
    1. In Rotation Type list box, choose By Time.
    2. In Begin Rotation Time field, enter the start time.

      Use the following java.text.SimpleDateFormat format to specify a date and time: MM-DD-yyyy-k:mm:ss.

      At the time that you specify, the server rotates the current log file. If the time that you specify is already past, the server starts its file rotation immediately. Thereafter, the server rotates the DataSource Profile log file at an interval that you specify in Rotation Interval.

    3. In the Rotation Interval field, enter the interval at which the server saves old DataSource profile records to another file.
  8. In the Log File Rotation Directory field, enter the directory location where the rotated log files will be stored.

    Enter an absolute pathname or a pathname that is relative to the server's root directory. By default, the rotated files are stored in the same directory where the log file is stored.

  9. Click Save.
  10. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

After you finish

Restart the server.


Back to Top