Administration Guide

Monitoring the Server

This chapter describes how to monitor a running BEA Liquid Data for WebLogic server. It includes the following sections:

Monitoring Liquid Data Server Statistics

The Liquid Data node in the Administration Console includes a Monitoring tab for monitoring the current status of the Liquid Data Server.

To view the status:

In the left pane, click the Liquid Data node.

In the right pane, click the Monitoring tab.

The Administration Console displays a list of managed objects. Figure 20-1 Monitoring Tab on the Liquid Data Node

The Monitoring tab displays statistics that are described in the following table:

Table 20-2 Monitoring Statistics for the Liquid Data Server

Field	Description
Number of Active Queries	Number of active queries.
Number of Data Sources	Number of configured data sources.
Number of Failed Queries	Number of failed queries.
Number of Cached XQuery Plans	Indicates the total number of XQuery plans currently cached in memory. A query with a cached plan does not require query compilation the next time it is run. For example, if you have 10 stored queries and of these you have executed only two queries (one or more times each), then the query cache will have the following entries: 2 (queryName1, queryName2)
Server Start Time	Date and time when the Liquid Data Server was started.
Number of Queries Succeeded	Number of queries successfully executed.
Thread Pool Size	Size of the thread pool.
Number of Queries Executed	Total number of queries (both successful and unsuccessful) executed since the Liquid Data Server was started.

Monitoring the Server Log

If logging is enabled on your WebLogic Server installation, the server log files contain information about the time spent to compile and execute a query. For more information, see Server Log in the WebLogic Server documentation

Custom applications can contain debugging calls to stdout that record times when Liquid Data compiles a query, submits the query to a data source for processing, receives the results from the data source, and processes the results. For more information, see Using WebLogic Logging Services.

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 such resources as servers, JDBC connection pools, JCA, HTTP, the JTA subsystem, JNDI, and EJBs. 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.