|bea.com | products | dev2dev | support | askBEA|
|e-docs > WebLogic Server > Configuring and Managing WebLogic Server > Monitoring a WebLogic Server Domain|
Configuring and Managing WebLogic Server
Monitoring a WebLogic Server Domain
These sections describe WebLogic Server monitoring capabilities that help you manage and optimize application availability, performance, and security:
Facilities for Monitoring WebLogic Server
These sections describe WebLogic Server facilities for monitoring the health and performance of a WebLogic Server domain:
The WebLogic Server Administration Console provides visibility into a broad array of configuration and status information.
The Administration Console obtains information about domain resources from the domain's Administration Server. The Administration Server 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:
When you access a monitoring page for particular resource in the Administration Console, the Administration Server performs a GET operation to retrieve the current attribute values.
For details on what data is available on specific console pages, see Monitoring WebLogic Server using the Administration Console.
Server Self-Health Monitoring
WebLogic Server provides a self-health monitoring feature to improve the reliability and availability of server instances in a domain. Selected subsystems within each server instance monitor their health status based on criteria specific to the subsystem. If an individual subsystem determines that it can no longer operate in a consistent and reliable manner, it registers its health state as "failed" with the host server instance.
Each server instance checks the health state of all its registered subsystems to determine the overall viability of the server. If one or more critical subsystems have reached the "failed" state, the server instance marks its own health state as "failed" to indicate that the it cannot reliably host an application.
When used in combination with Node Manager, server self-health monitoring enables you to automatically reboot servers that have failed. This improves the overall reliability of a domain, and requires no direct intervention from an administrator. See Node Manager Capabilities for more information.
Obtaining Server Health Programmatically
You can check the self-reported health state of a server instance programmatically by calling the getHealthState() method on the ServerRuntimeMBean. Similarly, you can obtain the health state of a registered WebLogic Server subsystem by calling the getHealthState() method on its MBean. The following MBeans automatically register their health states with the host server:
See the Javadocs for WebLogic Classes for more information on individual MBeans.
Messages and Log Files
WebLogic Server records information about events such as configuration changes, deployment of applications, and subsystem failures in log files. The information in log files is useful for detecting and troubleshooting problems, and monitoring performance and availability.
For detailed information about log files and the WebLogic Server logging subsystem, see "Logging" in Administration Console Online Help.
WebLogic Server outputs status and error messages to:
If you start a Managed Server with Node Manager, Node Manager redirects the server instance's standard out to a file. In this case, you can view the Managed Server's output using Domain
If you start a Managed Server with Node Manager, Node Manager redirects the server instance's standard error to a file. In this case, you can view the Managed Server's output using Domain
Monitoring WebLogic Server using the Administration Console
The left pane of the Administration Console is a tree control, with a node for key entities you have configured. The following sections list the attributes displays on monitoring pages in each node:
Domain Monitoring Pages
You can access one WebLogic domain at a time using the Administration Console. The Domain
Other Domain Monitoring Links
Each domain-level monitoring page has links to display:
Server Monitoring Pages
When expanded, the Servers node lists each server instance in the current domain. To monitor key run-time attributes for a server instance, click on its name, and choose one of Monitoring tabs. The monitoring pages available depend on the application objects deployed to the server instance. The following table lists the monitoring pages available for a server instance, and the attributes displayed on each page.
Other Server Monitoring Links
Each top level tab page for a server instance—Performance, Security, JMS, JTA— has links to display:
Clusters Monitoring Pages
The following table lists the monitoring pages available for a cluster, and the attributes displayed on each page
Machines Monitoring Pages
The following table lists the monitoring pages available for a machine, and the attributes displayed on each page.
Deployments Monitoring Pages
The following table lists the monitoring pages available in the Deployments Node, and the attributes displayed on each page
Services Monitoring Pages
The following table lists the monitoring pages available in the Services node, and the attributes displayed on each page.