![]() |
![]() |
|
Overview of Management Services
Some BEA Systems, Inc. customers choose to use WebLogic Server by configuring and deploying the software without any additional enhancements. This approach works for the vast majority of WebLogic Server users. A specific type of customer, sometimes referred to as an independent software vendor (ISV) or third-party developer, purchases special licenses for BEA software that allows such customers to build their own products on top of BEA's core technologies.
The following sections provide overviews of WebLogic Server services and interfaces that you use to customize WebLogic Server:
Advantages of the WebLogic Server Development Environment
As the leading e-commerce transaction platform and the first independently developed Java application server to receive J2EE certification, WebLogic Server provides a plug-and-play environment for creating multitier enterprise applications. J2EE APIs are implemented to work in an integrated manner with WebLogic Server services and facilities sharing common elements and objects.
WebLogic Server offers the independent developer:
The WebLogic Server management architecture is based on the Sun Microsystems Java Management Extensions (JMX) specification. Configuration is done using management beans, or MBeans, which retrieve their values from the domain configuration and state. MBeans provide developers with a means to access all configuration and monitoring information about WebLogic Server programmatically via the JMX standard API. An adminstrative domain represents a group of servers, clusters, or both servers and clusters, which must be administered together. The configuration information is stored in a configuration repository. The only repository supported for BEA WebLogic 6.0 is an XML file-based repository.
For more detailed information, see the following WebLogic Server documentation:
WebLogic Server Management Beans (MBeans) are based on Java Management Extensions (JMX) for server configuration and server run time data. For the MBean interfaces exposed via JMX, see the WebLogic Server API Reference. The MBean interfaces are documented as follows:
An MBean is an object that implements an interface using a "getter," a "setter," or an operation.
There are three types of MBeans:
An administration MBean and its corresponding configuration MBbean implement the same interface. At any point in time the configuration MBeans contain the property values actually being used by the server. Any configuration changes are applied to administration MBeans, and these changes are propagated to the relevant configuration MBeans, when appropriate.
The following example of an MBean interface declares one read-only attribute (Foo), one read/write attribute (Bar), one collection attribute (Baz), and one operation (deploy).
public interface FooMBean {
int getFoo();
BarMBean getBar();
void setBar(BarMBean bar);
BazBean[] getBaz();
void addBax();
void removeBaz();
void deploy()
}
See also Programming WebLogic Server MBeans.
Domains, the Administration Server, and Managed Servers
A WebLogic Server domain is an inter-related set of WebLogic Server resources managed as one unit. A domain includes one Administration Server and zero or more managed servers. It can include WebLogic Server clusters.
An Administration Server is a WebLogic Server that runs the Administration Service. The Administration Service is the central point of control for configuring and monitoring the domain. The Administration Server must be running in order to perform any kind of managment operation on that domain.
Typically, the applications and components with your business logic are deployed across Managed Servers, and the Administration Server is used to configure and monitor the Managed Servers.
The Administration Server must be running in order to perform any kind of management operation. For detailed information about the WebLogic Server management architecture, see the WebLogic Server Administration Guide.
Detailed information about the WebLogic Server domain configuration is available in the Administration Guide section "Domain Configuration."
Each WebLogic Server domain configuration is stored in an XML file-based repository named config.xml. The config.xml file resides in a subdirectory with the same name as the domain. An example of the default config.xml file is provided in the WebLogic Server Configuration Reference.
Warning: Manual editing of the config.xml file is not recommended. Customers who want to change their default WebLogic configurations are strongly urged to use the Administration Console to make configuration changes.
When manual editing of the config.xml file is required, make a backup copy of your original config.xml file prior to incorporating any changes.
See also the WebLogic Server Programming Guide Programming WebLogic XML.
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|