6 Monitoring Content Server Log Files

This chapter provides information on finding and using Content Server status information and errors in log files.

This chapter includes the following topics:

Introduction to Managing Content Server Log Files

Oracle WebCenter Content stores status information and errors in log files. Log files are used to register system events, with their date and time of occurrence. They can be valuable tools for troubleshooting, especially if verbose logging is turned on. Not only do logs indicate that specific events occurred, they also provide important clues about a chain of events that led to an error or problem.

Note:

When applied to trace log output, verbose logging can quickly increase the size of a log file and possibly cause the Content Server instance to slow down. It is recommended that for trace logs, verbose logging is only used when troubleshooting a specific issue. Content Server logs for system events do not have this issue with verbose logging.

For information on troubleshooting, see Troubleshooting Oracle WebCenter Content. For information on viewing system audit information, see Monitoring Content Server Status .

Information is also captured in logs controlled by Oracle Fusion Middleware Control and the Oracle WebLogic Server Administration Console using Oracle log APIs. The WebCenter Content interface provides access to these logs. For more information about using Fusion Middleware Control to monitor logs, see Managing Log Information Using Fusion Middleware Control.

About Content Server Log File Characteristics

Log files associated with the Content Server instance have the following characteristics:

  • They are created only once each day at the time the first status, error, or irrecoverable error occurs.

  • No empty log files are generated.

Each log file contains the following columns:

  • Type: Specifies the kind of incident that prompted the log entry: Information, Error, or Fatal.

  • Time: Lists the date and time the log entry occurred.

  • Description: Describes the incident that occurred.

The log files are standard HTML pages and are maintained for each Content Server instance. Logs are kept in revolving file name format for a maximum of 30 files. When the 31st file is created, the oldest one is deleted. Therefore, log file names in Content Server bear no relation to the date they were generated. To find a certain day in the log file, view the index file in a browser and select that day's link. The file name is displayed in the browser's status bar (if it is enabled).

Note:

Bookmark your log file pages. This will help you to troubleshoot problems, even if the Content Server instance is unavailable. Also, know where your configuration files are so you can find them if the Content Server instance is unavailable.

Accessing Content Server Logs

The Content Server logs are listed by date and time. One file is generated for each day. Entries are added to the file throughout the day as events occur.

The following types of server log entries are generated:

  • Info: Displays basic status information. For example, status information is logged if the server is ready and waiting.

  • Error: Displays errors that occur but do not stop the software from functioning. For example, an error is logged if a user requests secure information that they are not allowed to access.

  • Fatal: Displays errors that stop the software from functioning. For example, a fatal error is logged if the Content Server instance cannot access the database.

To access a Content Server log:

  1. Log in to the Content Server instance as an administrator.
  2. Choose Administration, then Log Files.
  3. Select Content Server Logs.
  4. On the Content Server Logs page, select the link that corresponds to the date and the time of the log that you want to view.

    Note:

    You must be logged in to the Content Server instance as an administrator to be able to view the log files.

    If, for whatever reason, you cannot view the log files from the Administration tray or menu, you can also access them on the file system of the Content Server instance. The log files can be found in these locations:

Log Files Found in:

Content Server

IntradocDir/weblayout/groups/secure/logs

Console Output Logs

IntradocDir/bin/classname.log

Refinery

IntradocDir/weblayout/groups/secure/logs/refinery

Archiver

IntradocDir/weblayout/groups/secure/logs/archiver

Accessing Archiver Logs

Content Server Archiver logs show information about imports, exports, and replications. The Archiver logs are listed by date and time. They are generated once a day when the first Archiver information status, fatal error, or error occurs.

The following types of Archiver log entries are generated:

  • Info: Displays basic status information. For example, status information is logged when an export and an import starts and finishes.

  • Error: Displays user/administration errors that occur but do not stop the software from functioning. For example, an error is logged if there is no file information for a content item that you are trying to export.

  • Fatal: Displays errors that stop the software from functioning. For example, a fatal error is logged if the Content Server instance cannot access the database. Check the connection string, user name, and password.

To access an Archiver log:

  1. Log in to the Content Server instance as an administrator.
  2. Choose Administration, then Log Files, then select Archiver Logs. Alternately, click the Archiver Logs link on the Administration page.
  3. On the Archiver Logs page, select the link that corresponds to the date and the time of the log.

    A table showing the type, date and time, and description of each action opens. The table also includes the name of the Content Server instance that created the archive.

Accessing Inbound Refinery Logs

All Oracle WebCenter Content: Inbound Refinery logs are accessed through the Inbound Refinery interface. For information on monitoring Refinery status through log files, see Inbound Refinery in Managing Oracle WebCenter Content.