|
Communicating Events Using JMX Notifications
This chapter explains how to use JMX notifications to communicate events to management applications (in this case, iPortal Administrator). This chapter uses the iBank example to illustrate the steps involved.
|
|
Superior app management with JMX
Ever heard of JMX? If you think it's just a sideline framework, think again. Java Management Extensions (JMX) is becoming a core part of application development and management. Many J2EE vendors, such as JBoss, Enhydra, and WebLogic, are using it. Read on for an introduction to JMX, followed by a hands-on example for using it with JSP. Take a step forward in implementing JMX into your own development environment.
|
|
Using WebLogic Server MBean Notifications
To report changes in configuration and runtime information, all WebLogic Server MBeans emit JMX notifications. A notification is a JMX object that describes a state change or some other specific condition that has occurred in an underlying resource.
|
|
Sending Notifications from MBeans
Management applications need to react to a state change or to a specific condition when it occurs in an underlying resource. AdventNet JMX implementation supports JMX Notification Model which allows MBeans to broadcast such management events, which are called Notifications. To receive the broadcasted Notifications, management applications and other objects register as listeners with the broadcaster MBean. The MBean notification model of JMX enables a listener to register only once and still receive all different events that may occur in the broadcaster.
|
|
Java application management on tap
AdventNet last week announced a new version of its management software aimed at helping users monitor Java application servers, along with the applications they host and back-end databases.
|
|
Dynamic Management of Internet Telephony Servers
|
|
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.
|