11 Diagnostics and Logging Facilities in Discoverer

11.1 What Discoverer diagnostics and logging capabilities are available?

Discoverer provides the following diagnostics capabilities to help you trace and diagnose problems. For example, if performance is slow, you might want to check whether the Discoverer middle tier components are configured correctly.

• Log files:

  • Discoverer Services log files

    For more information, see Section 11.3, "How to view Discoverer log files using Fusion Middleware Control."

  • Log files for Discoverer Plus, Viewer, Portlet Provider, and Web Services

    For more information, see Section 11.3, "How to view Discoverer log files using Fusion Middleware Control."

• CollectLogs script

  You can use the collectlogs utility to collect all Discoverer logs into a single location.

  For more information about using the collectlogs script, see Section 11.5, "How to copy Discoverer log files").

• CheckDiscoverer utility

  You can use the checkdiscoverer utility to verify a Discoverer configuration and report on failures or anomalies. For more information about the utility, see Section 11.2, "What is the checkdiscoverer utility?"

• Diagnostic utility for Discoverer Plus (OLAP).

  For more information, see Section 5.6, "Configuration diagnostic utility for Discoverer Plus OLAP").

• Log messages

  From the Farm menu, select Monitoring, and then select Logs to go to the Log Messages page, where you can search for and select log files to view. For more information, see Section 11.3, "How to view Discoverer log files using Fusion Middleware Control."

Notes

• When diagnosing Discoverer session information, you often must know the session ID of the Discoverer Plus session to monitor. A session ID uniquely identifies a session, which starts when an end user logs in to Discoverer and finishes when an end users logs out of Discoverer. You can use this session ID to locate the corresponding server log.

  If Single Sign-On is deployed, you can use the Single Sign-On user name to monitor Discoverer sessions.

  To find out the session ID of a Discoverer Plus user's session, access the JConsole of the Discoverer Plus user and note the Session ID: <number> value.

11.2 What is the checkdiscoverer utility?

The checkdiscoverer utility is a script that checks the configuration of the Discoverer middle tier and middle-tier components, and reports any failures or anomalies.

For more information about the checkdiscoverer utility, see Section A.1, "Discoverer file locations".

Note: Discoverer Plus OLAP has its own diagnostics utility. For more information, see Section 5.6, "Configuration diagnostic utility for Discoverer Plus OLAP").

11.3 How to view Discoverer log files using Fusion Middleware Control

The Enterprise Manager Fusion Middleware Control enables you to search for and view log files for Oracle Fusion Middleware applications. For example, you might want to examine a list of all Discoverer sessions running on a particular Discoverer middle-tier machine.

To view log files by using Fusion Middleware Control:

1. Start Enterprise Manager Fusion Middleware Control.

   For more information, see Section 4.1.2, "How to start Fusion Middleware Control and display the Farm Home page."

2. Navigate to the Discoverer home page.

   For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

3. From the Discoverer menu, select Monitoring, and then select Logs.

   The Log Messages page is displayed.

4. (optional) To search for a specific log file, enter the search criteria and click Search.

5. To view a list of the log files, click the Log Files... button.

   The Log Files page is displayed.

6. Select the row corresponding to the log file that you want to view, and click View Log File.

   The View Log File page is displayed. It shows the entries in the selected log file.

7. To view details of specific log entries, select the entries.

   The details of the selected log entry are displayed below the list of entries.

For more information, see Enterprise Manager Fusion Middleware Control Help.

11.4 How to set the log level for Discoverer component loggers

Oracle Fusion Middleware provides the following loggers for Discoverer components:

• ORACLE.DISCOVERER.SERVER: For Discoverer session server

• ORACLE.DISCOVERER.VIEWER: For Discoverer Viewer

• ORACLE.DISCOVERER.WEB_SERVICES: For Discoverer Web Services

• ORACLE.DISCOVERER.PORTLET_PROVIDER: For Discoverer Portlet Provider

• ORACLE.DISCOVERER.MODEL: For logging messages pertaining to common internal components that are used by the Viewer, Plus, and Web Services components

For each of these loggers, you can configure the Oracle Diagnostic Logging (ODL) level. You set the log level for individual Discoverer components when you want to monitor Discoverer component session activity at a specific level of detail.

To configure the log level for Discoverer component log files:

1. Start Fusion Middleware Control. For more information, see Section 4.1.2, "How to start Fusion Middleware Control and display the Farm Home page."

2. Navigate to the Fusion Middleware Control Discoverer home page. For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

3. From the Discoverer menu, select Logs, and then select Log Configuration.

   The Log Configuration page is displayed.

4. From the View list, select Runtime Loggers.

5. Select a logging level for each Discoverer component from the Oracle Diagnostic Logging Level (Java Level) list.

6. Click Apply.

   You can now monitor the Discoverer session log file at the level of detail that you specified. For more information, see Section 11.3, "How to view Discoverer log files using Fusion Middleware Control."

   For more information, see "Managing Log Files and Diagnostic Data" in the Oracle Fusion Middleware Administration Guide.

11.5 How to copy Discoverer log files

You might want to copy all Discoverer logs into a single location (for example, to provide a snap shot of a Discoverer middle-tier machine, or to provide an archive of Discoverer log files).

You use the collectlogs utility to copy Discoverer logs into a single location.

To copy Discoverer log files to a single location, run the following command on the Discoverer middle-tier machine.

collectlogs <logs_target_location>

The target location is either a TAR filename (UNIX) or a folder name (Windows).

The Discoverer log files are copied to the specified location.

For more information about the collectlogs utility, see Section A.1, "Discoverer file locations."