Chapter 2. The JBoss JMX Microkernel

IN THIS CHAPTER

• JMX

• The JBoss JMX Implementation Architecture

• Connecting to the JMX Server

• Using JMX as a Microkernel

• The JBoss Deployer Architecture

• Exposing MBean Events via SNMP

• Remote Access to Services, Detached Invokers

Modularly developed from the ground up, the JBoss server and container are completely implemented using component-based plug-ins. The modularization effort is supported by the use of JMX, the Java Management Extensions API. By using JMX, industry-standard interfaces help manage both JBoss server components and the applications deployed on it. Ease of use is still the number-one priority, and the JBoss Server architecture sets a new standard for modular plug-in design as well as ease of server and application management.

This high degree of modularity benefits application developers in several ways. The already tight code can be further trimmed down to support applications that must have a small footprint. For example, if EJB passivation is unnecessary in an application, you can simply take the feature out of the server. If you later decide to deploy the same application under an application service provider (ASP) model, you can simply enable the server's passivation feature for that web-based deployment. Another example is the freedom you have to drop your favorite object-to-relational database (O-R) mapping tool, such as TOPLink, directly into the container.

This chapter introduces you to JMX and its role as the JBoss server component bus. It also introduces you to the notion of JBoss MBean services, which add life cycle operations to the basic JMX management component.