Java Dynamic Management Kit 3.2 Programming Guide | ||||
---|---|---|---|---|
![]() | ![]() | Chapter 1. Introduction to the Java Dynamic Management Kit | ![]() | ![]() |
Benefits of the Java Dynamic Management Kit include:
Dynamic extensibility and scalability
Easy management of Java applications
Easy development of smart agents
Protocol independence
The Java Dynamic Management Kit eases the development of extensible agents. An agent is able to instantiate Java classes loaded from an arbitrary location. Therefore, it is possible to extend the functionality of a running agent by making new classes available at an arbitrary location and requesting the agent to load and instantiate them.
Agents developed using the Java Dynamic Management Kit are also scalable. M-beans can be registered and unregistered with the framework in an agent while it is running. By registering and unregistering new m-beans, the agent can use only what it needs when it needs it. This feature enables the size and complexity of an agent to be modified while the agent is running, without having to stop the agent.
The framework enables easy management of Java applications. For a Java application to be manageable, it only needs to be modified so that it:
Instantiates the framework and an adaptor
Registers the objects that, in conjunction with their states, accurately represent the application
The only restriction is that the registered objects have to be instances of an m-bean. This is not a serious restriction, as it does not force the existing design to be changed, nor does it require a fixed class inheritance scheme. When you design an m-bean, you do not need explicitly to take account of the interaction of the m-bean with the framework or the adaptors. This is handled for you by the design patterns for m-beans.
An application that includes the framework and an adaptor provides remote access for management operations without the need for any further development.
Agents developed using the Java Dynamic Management Kit are smart agents. A smart agent provides the services needed to process management requests. In a smart agent, much of the processing can be done locally in the agent itself, reducing the load on the network connection between the agent and the manager. This also enables an agent to continue to work if the connection between it and its manager is lost.
The design patterns for m-beans do not depend in any way on the protocol an agent uses for communicating with external applications. This is because the adaptors interact with m-beans through the framework. New adaptors (with new protocols) can be developed and used without rewriting existing m-beans or external applications. All that is required is that the new adaptor is able to interact with the framework.
![]() | ![]() | ![]() |
Key Concepts | ![]() | Product Components |