M-Beans

A managed bean, or m-bean, is a Java object that conforms to certain design patterns. These design patterns are derived from the JavaBeans^TM component model. They enable properties, actions, and events to be defined for an m-bean. They also enable you to make the distinction between a read-only and a read-write property in an m-bean. To comply with the design patterns for m-beans, an m-bean must be a JavaBeans component.

An m-bean instance is manageable as soon as it is registered with the framework. An m-bean can be instantiated and registered by:

• An agent

• A manager through an adaptor in an agent

Any object that you want to be accessible through the framework must be represented as an m-bean. Such objects include:

• The resources you want an agent to manage

• Services you want to provide for managing resources

You write the m-beans representing these objects yourself. Some components of the Java Dynamic Management Kit are implemented as m-beans.

While an agent is running, the m-beans are stored in memory.

All the information in memory is lost when the agent is stopped. When an agent is started, it has to reload the information into the repository. Compiled m-bean classes can be stored at any location specified in the CLASSPATH environment variable of the agent.