To integrate third-party management systems with the WebLogic Server management system, WebLogic Server provides standards-based interfaces that are fully compliant with the Java Management Extensions (JMX) specification. Software vendors can use these interfaces to monitor WebLogic Server MBeans, to change the configuration of a WebLogic Server domain, and to and monitor the distribution (activation) of those changes to all server instances in the domain. While JMX clients can perform all WebLogic Server management functions without using BEA’s proprietary classes, BEA recommends that remote JMX clients use WebLogic Server protocols (such as T3) to connect to WebLogic Server instances.
This document describes creating JMX clients that monitor and modify WebLogic Server resources.
The following sections describe the contents and organization of this guide—Developing Custom Management Utilities with JMX.
This document is a resource for software vendors who develop JMX-compatible management systems. 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 Java EE and general application management concepts. 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 the following documents:
As of release 10.0, WebLogic Server supports the
jmx.remote.x.request.waiting.timeout environment parameter. (The JMX Remote API 1.0 specification states that support for this parameter is optional.) Use this parameter to specify the number of milliseconds that your JMX client waits for the invocation of an MBean server method to return. If a method does not return by the end of the timeout period, the client moves to its next set of instructions. By default, a client waits indefinitely for a method to return; if the MBean server is unable to complete an invocation, the JMX client will hang indefinitely.
For more information, see Make Remote Connections to an MBean Server.