Skip navigation.
Downloads | Product Documentation | Support

Administration Guide

# Using Logging Information

This chapter describes how to monitor a running WebLogic Server that has at least one Liquid Data project.

The chapter contains the following sections:

- Monitoring the Server Log
- Monitoring a WebLogic Domain
- Using Other Monitoring Tools

For information on data service monitoring, see Monitoring Applications.

# Monitoring the Server Log

Server log files contain information about the time spent to compile and execute a query. The log is in the following location:

>     <BeaHome>\user_projects\domains\<domainName>\<serverName>\<server>.log

For more information about WebLogic Server logs, see "Viewing the WebLogic Server Logs" at:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/logging/viewing.html

You can configure the log levels, by application, using the General application configuration page. For more information, see General Application Settings. The log levels include:

- Error. Runtime exceptions.
- Notice. Possible errors that do not affect runtime operation, as well as error level events.
- Information. Start/stop events, unsuccessful access attempts, query execute times, and so on, as well as error and notice level events.

Debug logging occurs by default for any server in development mode. Client applications can contribute to the server log through the WebLogic logger facility. For more information, see "Using WebLogic Logging Services at:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/logging/use_log.html

Query strings are echoed in the server log as a debug-level log message when the log level is set to Information in the Liquid Data Console and the WebLogic Server Administration Console is set to log debug messages to stdout.

# Monitoring a WebLogic Domain

You can use the WebLogic Server Administration Console to monitor the health and performance of the domain in which WebLogic is deployed, including resources such as servers, JDBC connection pools, JCA, HTTP, the JTA subsystem, JNDI, and Enterprise Java Beans (EJB).

The domain log is located in the following directory:

>     <BeaHome>\user_projects\domains\<domainName>\<domainName>.log

For more information, see Monitoring a WebLogic Server Domain in Configuring and Managing WebLogic Server.

# Using Other Monitoring Tools

You can use performance monitoring tools, such as the OptimizeIt and JProbe profilers, to identify Liquid Data application "hot spots" that result in either high CPU utilization or high contention for shared resources.

For more information, see Tuning WebLogic Server Applications. For a complete list of performance monitoring resources, see Related Reading in WebLogic Server Performance and Tuning.