2.1. Why We Need JMX2.1.1. Choosing a Management Technology2.1.2. Dealing with Diversity2.1.2.1. Centralized Applications2.1.2.2. Distributed Applications2.1.2.3. Internet Applications2.1.2.4. E-Business Applications2.1.2.5. Service-Oriented Applications2.1.3. Being Managed by Multiple Management Applications2.1.4. Supporting Application-Specific Management Systems2.2. Which Applications Should Be Manageable?2.2.1. Complex Applications2.2.2. High-Volume Applications2.2.3. Mission-Critical Applications2.2.4. Corporate Applications2.2.5. Applications with Expectant Customers2.3. The Goals of JMX2.3.1. Simple API2.3.2. Dynamic Management2.3.3. Isolation2.3.4. Generic Management2.4. History2.4.1. JMAPI2.4.2. JDMK2.4.3. JMX2.4.4. The Specification and Compliance2.4.4.1. Compliance at the Instrumentation Level2.4.4.2. Compliance at the Agent Level2.4.4.3. Support at the Agent Level2.4.4.4. Compliance at the Distributed Services Level2.4.4.5. Compliance at the Management Level2.4.5. The Reference Implementation2.5. JMX Overview2.5.1. JMX-Managed Resources2.5.2. MBeans2.5.2.1. Standard MBeans2.5.2.2. Dynamic MBeans2.5.2.3. Open MBeans2.5.2.4. Model MBeans2.5.3. JMX Agents2.5.3.1. The MBeanServer2.5.3.2. Required Services2.5.4. JMX Adapters2.5.5. Adapter Tools2.6. Quick Tour of JMX2.6.1. todd, the Time of Day Daemon2.6.2. todd Management2.6.3. todd's MBeans2.6.4. Incorporating an MBeanServer2.6.5. Monitoring todd2.6.6. Browser Control2.7. SummaryNotes