Technical data
9 Monitoring a WebLogic Server Domain
9-2 Configuring and Managing WebLogic Server
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:
! Configuration MBeans, which control the domain’s configuration, and
! Run-time MBeans, which provide a snapshot of information about domain
resources, such as JVM memory usage. When a resource in the domain—for
instance, a Web application—is instantiated, an run-time MBean instance is
created which collects information about that resource.
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” on page 9-5.
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” on page 3-5 for more information.