Monitoring the Server

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

• Monitoring Liquid Data Server Statistics
• Monitoring the Server Log
• Monitoring a WebLogic Domain
• Using Other Monitoring Tools

 

---

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:

1. In the left pane, click the Liquid Data node.

2. In the right pane, click the Monitoring tab.

   The Administration Console displays a list of managed objects.

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

Table 18-1 Monitoring Statistics for the Liquid Data Server  

Field	Description
Active Queries	Number of active queries.
Data Source Count	Number of configured data sources.
Failed Queries	Number of failed queries.
Query Cache	Indicator of the total number of Xquery plans currently cached in memory. 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)
Start Time	Date and time when the Liquid Data Server was started.
Successful Queries	Number of successful queries.
Thread Pool Size	Size of the thread pool.
Total Queries	Total number of queries 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 Using Log Messages to Manage WebLogic Servers in the BEA WebLogic Server Administration Guide.

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 Creating and Configuring WebLogic Server Domains.

 

---

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 BEA WebLogic Server Performance and Tuning.