Java Dynamic Management Kit 3.2 Programming Guide
[ Previous ][ Fast Back ]Chapter 1. Introduction to the Java Dynamic Management Kit[ Fast Forward ][ Next ]

Product Components

The principal components of the Java Dynamic Management Kit are:

Framework

The framework is a registry for m-beans in an agent. It is introduced in The Core Management Framework. The framework also provides an event handling service, which receives event reports from m-beans and forwards them to any entity that has requested to receive them. For more information on the event handling service, refer to Event Handling Service in Chapter 15.

Adaptors

An adaptor connects the framework to external applications. The adaptors are introduced in Adaptors. For information on how to use the adaptors, refer to Chapter 5.

Services

To simplify the development of agents for network, system, application, and service management, the Java Dynamic Management Kit supplies a set of services. They are described in the following subsections.

Base Services

The base services are the services that the framework requires to be able to function. They are supplied as separate components to enable you to customize the framework by choosing the implementation you require from among those supplied. If you do not want to use the supplied implementation of a base service, you can further customize the framework by writing your own implementation and adding it to the framework. The base services are:

For more information on the base services, refer to Chapter 10.

Class and Library Loader Services

An agent uses the class loader to obtain new classes from an arbitrary location. The library loader loads native libraries into the framework. For more information on the class and library loader services, refer to Chapter 13.

M-Let Service

The management applet or m-let service enables an agent to obtain m-beans from a remote .jar file. For more information on the m-let service, refer to M-Let Service in Chapter 14.

Bootstrap Service

The bootstrap service simplifies the distribution of new releases of an agent from a central server. It is a standalone Java program that enables you to load an agent from a remote .jar file. To obtain a new version of an agent, run the bootstrap service on the system that requires the agent to be loaded and run. For more information on the bootstrap service, refer to Bootstrap Service in Chapter 14.

Launcher Service

The launcher service enables all the Java Dynamic Management applications running on a single machine to share the same base agent. It also enables you to load new applications into a base agent that is already running. For more information on the launcher service, refer to Launcher Service in Chapter 14.

Scheduler Service

The scheduler service enables you to create alarms for specific dates and times. The alarms or scheduler events are sent to all objects registered to receive scheduler events. It performs a function similar to that of the cron daemon of the UNIX® operating system. For more information on the scheduler service, refer to Scheduler Service in Chapter 15.

Alarm Clock Service

The alarm clock service activates (or "wakes up") alarm clock event listeners at regular intervals. It is used as the basis for the scheduler service. For more information on the alarm clock service, refer to Alarm Clock Service in Chapter 15.

Monitoring Service

The monitoring service enables the variation with time of a property in an m-bean to be monitored. For more information on the monitoring service, refer to Monitoring Service in Chapter 15.

Discovery Service

The discovery service enables agents to be discovered by clients by using multicasting. For more information on the discovery service, refer to Discovery Service in Chapter 15.

Cascading Agent Service

The cascading agent service enables you to implement a hierarchy of master agents and subagents. For more information on the cascading agent service, refer to Chapter 16.

Tools

These tools are provided with the Java Dynamic Management Kit:

Default Base Agent

To ease the testing of m-beans, the Java Dynamic Management Kit provides a base agent. This agent is ready to be started without further modification. It is a container in which m-beans can be instantiated and tested. This agent contains:

For information on how to start and stop the default base agent, refer to Appendix E.

SNMP Manager API

The SNMP manager API is a set of Java classes that simplifies the development of applications for managing SNMP agents. The agents may be developed with the Java Dynamic Management Kit, or by other means. For information on the SNMP manager API, refer to Chapter 20.


[ Previous ][ Home ][ Next ]
Benefits of the Java Dynamic Management Kit[ Up ]Overview of the Development Process