As an application developer, you can greatly reduce the cost of operating and maintaining your applications by building management facilities into your applications. The simplest facility is message logging, which reports events within your applications as they occur and writes messages to a file or other repository. Depending on the criticality of your application, the complexity of the production environment, and the types of monitoring systems your organization uses in its operations center, your needs might be better served by building richer management facilities based on Java Management Extensions (JMX). JMX enables a generic management system to monitor your application; raise notifications when the application needs attention; and change the configuration or runtime state of your application to remedy problems.
This document describes how to use JMX to make your applications manageable.
The following sections describe the contents and organization of this guide—Developing Manageable Applications with JMX.
This document is a resource for software developers who develop management services for J2EE applications. It also contains information that is useful for business analysts and system architects who are evaluating WebLogic ServerŪ or considering the use of JMX for a particular application.
It is assumed that the reader is familiar with J2EE and general application management concepts.
The information in this document is relevant during the design and development phases of a software project. This document does not address production phase administration, monitoring, or performance tuning topics. For links to WebLogic Server documentation and resources related to these topics, see Related Documentation.
This document emphasizes a hands-on approach to developing a limited but useful set of JMX management services. For information on applying JMX to a broader set of management problems, refer to the JMX specification or other documents listed in Related Documentation.
The Sun Developer Network includes a Web site that provides links to books, white papers, and additional information on JMX:.
To view the JMX 1.2 specification, download it from.
To view the JMX Remote API 1.0 specification, download it from.
You can view the API reference for the
javax.management* packages from: .
For guidelines on developing other types of management services for WebLogic Server applications, see the following documents:
For guidelines on developing and tuning WebLogic Server applications, see Developing Applications with WebLogic Server.
In addition to this document, BEA Systems provides two JMX code samples in the Avitek Medical Records Application (MedRec). MedRec is an end-to-end sample J2EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.
The JMX code in MedRec exemplifies the following management tasks:
A JSP and supporting Java classes in the MedRec application invoke JMX APIs to add a new Administrator user to the MedRec security realm. The JSP provides the interface for collecting the new user information and the supporting classes validate the information and insert the new user into the realm.
For information about the JMX code examples in MedRec, do the following:
As of this release, if you register custom MBeans in a WebLogic Server MBean server, you can use roles and policies along with the WebLogic Security Service to protect your MBeans. Note the following restrictions:
value" key property.
For information about creating XACML roles policies and adding them to your realm, seein Securing WebLogic Server Resource with Roles and Policies.
WebLogic Server 9.0 introduced several important changes to the WebLogic Server JMX implementation. Seein Developing Manageable Applications with JMX for WebLogic Server 9.0.