1. Mike Dickson Tidal Software mike.dickson@tidalsoft.com

2. Introduction From a little town called Gig Harbor, WA
Married with 5 children
Degree in CS from BYU
Former Sun Java Instructor
Bluestone
HP Middleware
HP Openview
Now at Tidal Software

3. Agenda JMX Overview JMX Implementation Architecture
JMX Definition
JMX MBeans Types
JMX MBean Server
JMX Implementation Architecture
Overall Architecture
Agent Architecture
Client Architecture
JMX Implementation Demo
Operations Views
Developer Views and Functinos
Please ask question all along

4. JMX Overview JMX – Java Management Extensions Started with JSR 3!
How to manage resources like devices or applications the Java way
It is accomplished by “Instrumenting” your code
Very comprehensive and well thought out
Started with JSR 3!
Scope
Application Configuration
Statistics
State Changes of Systems

5. JMX Overview
An MBean is a Java object that is instrumented to make Java systems manageable
They consist of:
Attributes
Methods
Notifications
Constructors
There are four types of MBeans:
Standard MBeans
Define Java Bean compliant Interface, then implement it
Static interface
Metadata is generated by the JMX Agent
Dynamic MBeans
Implement DynamicMBean interface
getAttibute, setAttribute, getAttributes, setAttributes, invoke, getMBeanInfo
More flexible and Dynamic
Developer creates the Meta Data
Standard MBeans
The simplest to design and implement.
Their management interface is described by their method names, just like Java Beans.
Dynamic MBeans
Implements specific interface expose their management interfaces at runtime for greatest flexibility.
Open MBean
Dynamic MBeans that rely on basic data types for universal manageability; they are self-describing for user-friendliness.
Model MBeans
Dynamic MBeans that are fully configurable and self described at runtime. They provide a generic MBean class with default behavior for dynamic instrumentation of resources.
Notification Model
JMX technology defines a generic notification model based on the Java event model. It lets developers build proactive management solutions. Using notifications, JMX agents and MBeans can send critical information to interested parties such as management applications or other MBeans.
MBean Metadata Classes
These classes contain the structures to describe all components of an MBean's management interface: its attributes, operations, notification, and constructors. For each of these, the metadata include a name, a description and its particular characteristics (for example, an attribute is readable, writeable, or both; for an operation, the signature of its parameter and return types).

6. JMX Overview Model MBeans Open MBean
Is a Dynamic MBean that uses Metadata Classes to describe features at the top of the slide
ModelMBean implements DynamicMBean
It is able to persist itself
Implements the ModelMBean interface
setModelMBeanInfo, setManagedResource
RequiredModelMBean is an implementation of this that must be in each JMX implementation
You don’t have to implement the ModelMBean interace just the meta data classes to describe your features
Open MBean
No specific interface that you have to implement other than DynamicMBean
The first three MBean types usually only describe the native Java data types and Strings They also allow arrays of those types
But what about complex data types?
Open MBeans “open” up MBeans to complex data types without the management application having to deal with user class file data types
They create a subclass of OpenType for attributes, methods, notifications, constructors

7. Notification Model MBean Server JMX Overview
Same as the normal Java Event Model
Broadcaster and Listeners
MBean Server
Like a RMI server
You register you MBeans
The Server does not need to be in the same JVM
Everything is an Interface
Connectors(Agents) talk to the MBean Server to do their magic

8. Tidal Intersperse – Architecture
Standards-Based
Interfaces
Monitored
Systems
Database
Web Service
HPOV/Tivoli/…
.NET
Java SE VM
Java EE
Java EE Cluster
JMS
Persistence
RDBMS
Services
LDAP
SOM
JMX Client
Browser
Web Services
Client
SNMP Client

9. Tidal Intersperse – Agent Architecture
Standard
Object
Model
Persistence
RDBMS
Services
LDAP
Intersperse
Middle
Tier
JMS Bus
Application Server
JMX
Server
Agent
Application

10. Tidal Intersperse – Client Architecture
Standard
Object
Model
Persistence
RDBMS
Services
LDAP
Intersperse
Middle
Tier
JMS Bus

11. JMX Implementation Demo
Intersperse 6.0