|
The MBean Server in a Minimal Agent
An agent application is a program written in the Java language which contains an MBean server and some way of accessing its functionality. This would be a minimal agent, anything less couldn't be managed. In our example of a minimal agent, we will access the MBean server through the HTML protocol adaptor from a web browser
|
|
Programming WebLogic Server MBeans
Using the J2EE Java Management Extensions (JMX) specification with the WebLogic Server Management API, developers can create and deploy Management Beans (or MBeans) to extend and customize WebLogic Server.
|
|
Exploring WebLogic JMX: JMX and J2EE, Part 1
J2EE is rapidly becoming an established platform for deploying long-running business-critical applications. As the number of J2EE applications grows and their importance increases, a standard way to manage J2EE servers and applications is becoming a key requirement.
|
|
Exploring WebLogic JMX: JMX and J2EE, Part 2
The Java Management Extensions (JMX) API provides a standard way of adding management capabilities to Java applications. BEA WebLogic 6.1 provides a full implementation of the JMX 1.0 specification, with all of its management features based on the JMX standard. As a result, the management capabilities in WLS are open and extensible, which makes it easy to build specialized management utilities for applications deployed on WLS.
|
|
Remote MBeanServers
It's possible to use the sample JSPs to manage an MBeanServer running in a different JVM than the ServletEngine JVM. You can use any JMX implementation you wish as long as there's a JMXServiceAdapter implementation available to wrap the remote MBeanServer reference. For example, there's an RMI based JMXServiceAdapter which uses the MX4J JMX Implementation to connect to a remote MBeanServer. The JMXServiceAdapter implementation that JMX type is called org.webjmx.adapter.RMIAdapter. Follow these steps to manage a remote MBeanServer using the MX4J JMX Implementation.
|
|
Interface MBeanServer
This is the interface for MBean manipulation on the agent side.
|
|
Managing Existing MBeans using SNMP
Existing standard or dynamic MBeans can be rendered manageable by generating a JMX agent for them, using ManageEngine JMX Studio. The management information contained in them is packaged as model MBean with an XML file, which has SNMP descriptors. It is registered with the MBean server. This opens the door for access to the management information via SNMP. The user is freed from the hassle of writing any Java code.
|
|
Using MBean Notifications
All WebLogic Server MBeans implement the javax.management.NotificationBroadcaster interfaces, which means they can emit standard JMX notification types.
|
|
AdventNet Agent Toolkit Java/JMX Edition 5.0
Most of the management systems are built from top to bottom either by SNMP, TL1 or HTTP. They leverage the specific facilities offered by the selected management protocol. For example, application server vendors are keen at SNMP for their management needs. Similarly TL1 is a man-machine management protocol deployed in broadband and access networks, including SONET networks. New technologies such as WDM and xDSL sometimes use the TL1 protocol for management of network equipment.
|
|
Framework for managing large scale component-based
distributed applications using JMX
This paper presents a extended Java Management eXtensions service developed for
the SmartFrog framework to provide a standard instrumentation layer for component-based
distributed systems.
|
|
Programming WebLogic Management Services with JMX
WebLogic Server managed resources are configured from the values in Local Configuration MBeans, which are replicas of the Administration MBeans on the Administration Server.
|
|
From black boxes to enterprises, Part 1: Beans, JMX 1.1 style
JMX is a popular new standard extension to the Java platform that enables devices, applications, and services to be managed, controlled, and monitored through modern Network Management Systems or Enterprise Management Systems. In this second article of his three-part series on JMX, consultant and popular author Sing Li demonstrates how to rapidly add instrumentation code to a Java-based application.
|
|
From black boxes to enterprises, Part 2: Beans, JMX 1.1 style
JMX is a popular new standard extension to the Java platform that enables devices, applications, and services to be managed, controlled, and monitored through modern Network Management Systems or Enterprise Management Systems. In this second article of his three-part series on JMX, consultant and popular author Sing Li demonstrates how to rapidly add instrumentation code to a Java-based application.
|
|
JMX and J2EE servers, a match in heaven?
JMX or Java Management eXtenstions are a new standard from Sun. It basically defines standards for writing JMX objects, also called MBeans and defines a standard for the container that hosts these MBeans. It's possible for a JMX client to invoke methods and access attributes on an MBean using the container. It's also possible for a client to register with another MBean and receive notifications from the MBean. So far, we're just taking about an application using a JMX container so that it can host MBean components in the application.
|
|
Score big with JSR 77, the J2EE Management Specification
The Java Community Process (JCP) has released the proposed final draft for the J2EE Management Specification, or Java Specification Request (JSR) 77. The specification's core is based on the model of managed objects, which Dirk Laessig explains in this article. JSR 77 also defines an Enterprise JavaBeans (EJB) component for easily accessing these managed objects.
|
|
JMX 1.2 Security
Access Control for the MBeanServer and its MBeans
This proposal extends the current JMX specification with features that allow administrators
to control access to the MBeanServer and individual MBean APIs.
|