Release History
Java DMK 5.1 (June 2004)This release conforms to the Java Management Extensions (the JMX Specification), v1.2 Maintenance Release, and JMX Remote API 1.0. Other major features added in this release:
Java DMK 5.0 (June 2002)This release conforms to the JMX Specification v1.1 Maintenance Release, March 2002. It includes an implementation of SNMPv3, based on RFCs 2571, 2572, 2574, and 2576. Java DMK 5.0 supports SNMPv1, SNMPv2c and SNMPv3 message processing models, and provides a user-based security model (USM) covering the USM MIB, authentication (HMAC MD5 and HMAC SHA) and privacy (DES). Other major features added in this release:
Java DMK 4.2 (December 2000)This release is the first commercial product to support the final release of the JMX specification v1.0 (July 2000). This support includes an implementation of Model MBeans, which are used for instrumenting resources programmatically at run-time.This release also focuses on providing a complete security mechanism. Context checking in the agent application allows management requests to be filtered based upon the type of request, the data in the request and a context object provided by the manager. The context can be used to identify managers and have them provide a password. The other major feature is the common methods between the MBean server and remote MBean server interfaces, introducing the concept of local, agent-side proxy objects. This new design allows many management components to be instantiated either in the agent or in the manager applications, thereby giving more flexibility and extensibility to management solutions.
Significant SNMP enhancements in this version extend
Java DMK 4.1 (April 2000)This release of the product significantly expanded the agent services which provide intelligence and autonomy in agent applications.
InformRequest commands, and agent MIBs supporting default
values and nested groups.
Java DMK 4.0 (December 1999)This was the first version of the product which conformed to the Java Management extensions defined by the JMX specification, v1.0 (Public Release 2 of December 1999). While the concepts of the Java Dynamic Management architecture remained the same, most implementation classes needed to be updated to match the specification.Shortly afterwards, a migration guide from version 3.2 to 4.0 was published to help programmers port their applications to the JMX architecture. The JMX compatibility introduced new concepts such as standard and dynamic MBeans, the management interface and its metadata description, a generic notification mechanism, and improved dynamic loading. This version also introduced improvements in the HTML adaptor, in HTTP and RMI connector performance, in notification forwarding through firewalls, and in the manager-side proxy objects. The SNMP toolkit also provided new support for tables in SNMP agent MIBs.
Java DMK 3.2 (March 1999)This was the first version of the Java Dynamic Management Kit on the Java 2 platform. In addition to porting all product functionality, this version added security based on the Java 2 security manager and customization based on Java properties.SNMP functionality was expanded by providing an example of an SNMP proxy, allowing agents to forward SNMP requests to other SNMP agents.
Java DMK 3.0 (November 1998)This early version of the product served as the input to the JMAPI 2.0 standardization effort, the precursor to the JMX specification. It refined and extended the concepts of a management architecture.It introduced new adaptors and access control for existing adaptors. It also provided more complete event handling in remote managers, as well as support for native libraries and signed JAR files. New functionality included the scheduling and discovery services.
Java DMK 3.0 provided SNMPv2 protocol support in the SNMP adaptor,
except for
Java DMK 2.0 (February 1998)This first commercial release introduced the concept of management through Java applications.This version developed the foundation of a management architecture: manageable resource beans, an agent framework, agent services and protocol adaptors, and client APIs for remote managers.
|
| |||||||||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||