Technical data

1 Overview of WebLogic Server Management
1-6 Administration Guide
Run-time and Configuration Objects
The Administration Server is populated with JavaBean-like objects called
Management Beans (MBeans), which are based on Sun’s Java Management Extension
(JMX) standard. These objects provide management access to domain resources.
The Administration Server contains both configuration MBeans and run-time MBeans.
Configuration MBeans provide both SET (write) and GET (read) access to
configuration attributes.
Run-time MBeans provide a snapshot of information about domain resources, such as
current HTTP sessions or the load on a JDBC connection pool. When a particular
resource in the domain (such as a Web application) is instantiated, an MBean instance
is created which collects information about that resource.
When you access the monitoring page for particular resources in the Administration
Console, the Administration Server performs a GET operation to retrieve the current
attribute values.
The Administration Service allows you to change the configuration attributes of
domain resources dynamically — while the WebLogic Servers are running. For many
attributes, you do not need to restart the servers for your change to take effect. In that
case, a change in configuration is reflected in both the current run-time value of the
attribute as well as the persistently stored value in the configuration file. (For more
information about configuring WebLogic Servers, see Configuring WebLogic Servers
and Clusters.)
In addition to the Web-based Administration Console, WebLogic Server provides a
command-line utility for accessing configuration and monitoring attributes of domain
resources. This tool is provided for those who want to create scripts to automate system
management. For more information, see:
n WebLogic Server Command-Line Interface Reference for information on using
the comman-line utility.
n BEA WebLogic Server Configuration Reference for information on using
Mbeans and the config.xml file.