Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs   |   Site Map   |   Search   |   Contact   |   Glossary   |   WebLogic Server Documentation
BEA WebLogic Server Administration Guide:   Previous topic   |   Next topic   |   Contents   |  Index

This section explains how to monitor your WebLogic domain, including:

• Overview of Monitoring

• Monitoring Servers

• Monitoring JDBC Connection Pools

• Summary of Monitoring Pages in the Administration Console

Overview of Monitoring

The tool for monitoring the health and performance of your WebLogic domain is the Administration Console. The Administration Console allows you to view status and statistics for WebLogic resources such as servers, HTTP, the JTA subsystem, JNDI, security, CORBA connection pools, EJB, JDBC, and JMS.

Monitoring information is presented in the right pane of the Administration Console. You access a page by selecting a container or subsystem, or a particular entity under a container, on the hierarchical domain tree, in the left pane.

The Administration Console provides three types of page that contain monitoring information:

• Monitoring tab pages for a particular entity (such as an instance of a JDBC Connection Pool or a particular server's performance)

• Tables of data about all entities of a particular type (such as the WebLogic Servers table)

• Views of the domain log and of the local server logs. For information about log messages, see Using Log Messages to Manage WebLogic Servers.

The Administration Console obtains information about domain resources from the Administration Server. The Administration Server, in turn, is populated with Management Beans (MBeans), based on Sun's Java Management Extension (JMX) standard, which provides the scheme for management access to domain resources.

The Administration Server contains both configuration MBeans, which control the domain's configuration, and run-time MBeans. Run-time MBeans provide a snapshot of information about domain resources, such as JVM memory usage or the status of WebLogic Servers. When a particular resource in the domain (such as a Web application) is instantiated, an MBean instance is created which collects information about that particular resource.

When you access a monitoring page for particular resources in the Administration Console, the Administration Server performs a GET operation to retrieve the current attribute values.

The following sections describe some of the monitoring pages that are useful for managing a WebLogic domain. These pages have been selected simply to illustrate the facilities provided by the Administration Console.

Monitoring Servers

The servers table and the monitoring tab pages for individual servers enable you to monitor WebLogic Servers. The servers table provides a summary of the status of all servers in your domain. If only a small subset of the log messages from the server are forwarded to the domain log, accessing the local server log may be useful for troubleshooting or researching events.

For more information about the log files and the logging subsystem, see Using Log Messages to Manage WebLogic Servers.

You can access monitoring data for each WebLogic server from the monitoring tabs for that server. The Logging tab provides access to the local log for the server (that is, the log on the machine where the server is running).

The MonitoringGeneral tab page indicates the current status and provides access to the JNDI tree, the Execute Queues table, the Active Sockets table, and the Connections table. The Execute Queues table provides performance information such as the oldest pending request and the number of requests currently pending.

Shutting down or Suspending a Server

The MonitoringGeneral tab also enables you to shut down or suspend a server. If a server is suspended, it accepts requests only from the Administration Server. Client requests are ignored.

Performance

The MonitoringPerformance tab graphs real-time data on JVM memory heap usage, request throughput, and waiting requests. This tab page also enables you to force the JVM to perform garbage collection on the memory heap.

The Java heap is a repository for Java objects (live and dead). Normally you do not need to perform garbage collection manually because the JVM does this automatically. When the JVM begins to run out of memory, it halts all execution and uses a garbage collection algorithm to free up space no longer used by Java applications.

On the other hand, developers debugging applications may have occasion to force garbage collection manually. Manual garbage collection may be useful, for example, if they are testing for memory leaks that rapidly consume JVM memory.

The MonitoringCluster tab provides information about the cluster that the selected server is a participant in (such as the number of servers in the cluster that are currently alive).

Server Security

The MonitoringSecurity tab provides statistics about invalid login attempts and locked and unlocked users.

The MonitoringJMS tab provides statistics on JMS servers and connections. This page also provides links to the tables of active JMS connections and active JMS servers, which monitor such attributes as total current sessions.

The MonitoringJTA tab provides statistics on the Java Transactions subsystem such as total transactions and total rollbacks. The page provides links to tables that list transactions by resource and name, and a table of in-flight transactions.

Monitoring JDBC Connection Pools

Java Database Connectivity (JDBC) subsystem resources can also be monitored via the Administration Console. The Monitoring tab for a JDBC connection pool allows you to access a table listing statistics for the instances of that pool. As with other entity tables in the Administration Console, you can customize the table to select which attributes you want to be displayed.

A number of these attributes provide important information for managing client database access.

The Waiters High field indicates the highest number of clients waiting for a connection at one time. The Waiters field tells you how many clients are currently waiting for a connection. The Connections High field indicates the highest number of connections that have occurred at one time. The Wait Seconds High field tells you the longest duration a client has had to wait for a database connection. These attributes allow you to gauge the effectiveness of the current configuration is in responding to client requests.

If the Connections High field value is close to the value of the Maximum Capacity field (set on the Configuration Connections tab), you might consider increasing the value of Maximum Capacity (the maximum number of concurrent connections). If the value in the Waiters High field indicates that clients are subject to a long wait for database access, then you might want to increase the size of the pool.

The value in the Shrink Period field is the length of time the JDBC subsystem waits before shrinking the pool from the maximum. When the subsystem shrinks the pool, database connections are destroyed. Creating a database connection consumes resources and can be time-consuming. If your system has intermittent bursts of client requests, a short shrink period might mean that database connections are being recreated continually, which may degrade performance.

Summary of Monitoring Pages in the Administration Console

|The following table lists all tables and monitoring tab pages available in the Administration Console.

Table 4-1 Summary of Monitoring Pages in the Administration Console

Page	Path to Page	Monitoring Data
Monitoring Tab Pages
General Server Information	servernameMonitoringGeneral	State and activation time
Server Performance	servernameMonitoring Performance	Real-time graphs of request throughput, JVM memory usage, and waiting requests
Cluster Statistics	servernameMonitoringCluster	Statistics about clusters such as the number of alive servers and sent and received fragments.
Server Security	servernameMonitoringSecurity	Number of invalid login attempts, total locked and unlocked users, and other security statistics
Server Version Information	servernameMonitoringVersion	JDK, WebLogic, and operating system versions
Cluster	ClustersclusternameMonitoring	Information about participating servers
Entity Tables
Servers	Servers	Server-specific data, such as memory usage, startup time, state, cluster participation, invalid login attempts, heap status, sockets counts, and total restarts
Execute Queues	servernameMonitoringGeneralMonitor Execute Queues on this server	Information about serviced and pending requests and other attributes
Execute Sockets	servernameMonitoringGeneralMonitor Active Sockets on this server	Protocol and other attributes of active sockets
Connections	servernameMonitoringGeneral Monitor Connections on this server	Connect time, remote address, bytes sent and received and other attributes of connections
Clusters	Clusters	Data such as default load algorithm and multicast address
Transactions By Name	servernameMonitoringJTA Monitor Transactions by Name on this server	Data about transactions organized by name
Transactions By Resource	servernameMonitoringJTA Monitor Transactions by Resource on this server	Data about transactions organized by resource
Active Transactions	servernameMonitoringJTA Monitor In-flight Transactions on this server	Data about in-flight transactions on this server
Machines	Machines	Address and other attributes of machines
Applications	Applications	List of applications
EJB Deployments	DeploymentsEJB	URL, application name, and other attributes for each EJB
Web Applications	DeploymentsWeb Applications	Data such as URL and default servlet for each Web application
Active Web Applications	DeploymentsWeb ApplicationsappnameMonitoringMonitor all instances of appname	Data about deployed copies of this Web application
Web Application Servlets	DeploymentsWeb ApplicationsappnameMonitoringMonitor all servlets for this Web Application	Statistics for the selected Web application, such as maximum pool capacity and execution time
Startup and Shutdown Classes	DeploymentsStartup & Shutdown	List of registered startup and shutdown classes
JDBC Connection Pools	ServicesJDBCConnection Pools	Initial capacity, capacity increment and other attributes of JCBC Connection Pools
JDBC Multipools	ServicesJDBCMultipools	Load balancing and other attributes of JDBC Multipools
JDBC Data Sources	ServicesJDBCData Sources	Pool name, JNDI name and other attributes of JDBC data sources
JDBC Tx Data Sources	ServicesJDBCTx Data Sources	Pool name, JNDI name and other attributes of JDBC Tx data sources
JMS Connection Factories	ServicesJMS Connection Factories	JNDI name, client ID, default priority and other attributes of JMS connection factories
JMS Templates	ServicesJMSTemplates	Data about JMS templates
JMS Destination Keys	ServicesJMSDestination Keys	Key type and other attributes of JMS destination keys
JMS Stores	ServicesJMSStores	Descriptions of JMS stores
JMS Servers	ServicesJMSServers	Data about JMS servers
Active JMS Services	ServicesJMSServersMonitor all Active JMS Services	High water mark of connections and other data about active JMS services
Active JMS Servers	ServicesJMSServersMonitor all instances	Statistics about sessions, messages pending, and other data
Active JMS Destinations	ServicesJMSServersMonitor all Active JMS Destinations	Consumers, messages received and other attributes of active JMS destinations
Active JMS Session Pools	ServicesJMSServersMonitoringMonitor all Active JMS Session Pools	High water mark of consumers and other monitoring data
JMS Destinations	ServicesJMSjmsservername Destinations	JNDI name and other data
JMS Session Pools	ServicesJMSjmsservername Session Pools	Acknowledge mode, maximum sessions, and other attributes of JMS session pools
XML Registries	ServicesXMLXML Registries	Lists of DocumentBuilderFactories and SAXParserFactories
WLEC Connection Pools	ServicesWLECWLEC Connection Pools	WebLogic Enterprise (WLE) domain name, failover addresses, maximum and minimum pool size, and other information
Jolt Connection Pools	ServicesJolt	Failover addresses, maximum and minimum pool size and other attributes of Jolt connection pools
Active Jolt Connection Pools	ServicesJolt joltconnectionpoolname MonitoringMonitor all active pools	Maximum capacity, current connections, and other data about instances of a Jolt connection pool
Virtual Hosts	ServicesVirtual Hosts	Format, logfile name and other attributes of virtual hosts
Mail Sessions	ServicesMail	Name and properties of mail sessions
File T3	ServicesFile T3	Name and path of files
Users	SecurityUsers	List of users
Groups	SecurityGroups	List of groups
Access Control Lists	SecurityACLs	List of ACLs
Caching Realms	SecurityCaching Realms	Lists caching realms
Realms	SecurityRealms	Describes realms
Domain Log Filters	Domain Log Filters	Servers on which the filter is registered and attributes used for filtering log messages