Technical data

1 Overview of WebLogic System Administration
1-6 Configuring and Managing WebLogic Server
Runtime Mbeans contain sets of attributes consisting of runtime information for active
WebLogic Servers instances and applications. By retrieving the values of attributes in
these runtime MBeans, you can monitor the running status of a WebLogic Server
domain.
Mbeans may also contain operations used to execute management functions.
Although users with a knowledge of these Mbeans and the JMX API can create their
own customized management system, most users prefer to use the system
administration tools provided with WebLogic Server to perform these tasks. These
tools do not require knowledge of the JMX API. For more information, see “System
Administration Tools” on page 1-8.
The Administration Server and Managed
Servers
One instance of WebLogic Server in each domain is configured as an Administration
Server. The Administration Server provides a central point for managing a WebLogic
Server domain. All other WebLogic Server instances in a domain are called Managed
Servers. In a domain with only a single WebLogic Server instance, that server
functions both as Administration Server and Managed Server.
For a typical production system, BEA recommends that you deploy your applications
only on Managed Servers. This practice allows you to dedicate the Administration
Server to configuration and monitoring of the domain.
For more information, see Starting and Stopping Servers.
Failover for the Administration Server
To prevent the Administration Server from becoming a single point of failure,
Managed Servers can always function without the presence an Administration Server,
but an Administration Server is required to manage and monitor the domain. By
maintaining backups of the
config.xml file and certain other resources for a domain,