 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 3: JavaTM Management Extensions (JMXTM) Specification
Reason: Withdrawn following Maintenance Review 6. JCP version in use: 2.9 Java Specification Participation Agreement version in use: 2.0 Description: The JMXTM specification will provide a management architecture, APIs and services for building Web-based, distributed, dynamic and modular solutions to manage Java enabled resources. Expert Group Transparency: Public Communications Issue Tracking Team
This JSR has been Withdrawn Note that this JSR was completed under JCP 2.1 and moved to JCP 2.6 in Maintenance.
2013.10.10:
Specification Lead: Hinkmond Wong E-Mail Address: hinkmond.wong Telephone Number: +1 408 276 7618 Fax Number: - The Maintenance Lead has provided the public Issue list and communications channel for feedback.
2012.03.21:
E-mail: staffan.larsen Telephone: +46 8 506 309 00
Original Java Specification Request (JSR) Identification | Request | Contributions Section 1: Identification
Submitting Participant: Sun Microsystems Consumer & Embedded Embedded System Software Group Director and General Manager: Jean Pierre Baudouin (baudouin@france.sun.com) Engineering manager: Dave Hendricks (dave.hendricks@france,sun.com) Marketing manager: Philippe Lalande (philippe.lalande@france.sun.com) Endorsers of the JSR: BullSoft Computer Associates Exide Electronics Jyra Research Lumos Tibco Tivoli Section 2: Request
- Target Java Platform
All platforms: Full Java, Personal Java and Embedded Java
JMAPI will make it possible to add manageability to Java
enabled equipment, from webphones and set-top boxes to network
devices and servers.
- Needs of Java Community Addressed
The Java Community needs a universal and modular Java
management foundation which addresses the following
requirements:
+ Allow rapid development of Java management solutions for
the following markets: consumer, enterprise computing,
telecommunications and datacommunications.
+ Provide a component-based architecture that scales from
small footprint devices to large telecom switches.
+ Allow for portability of management applications, by
supporting multiple hardware environments, protocols,
information models, databases...
+ Allow for dynamic upgrade of management capabilities.
+ Provide integration with legacy management systems.
- Why need not already addressed
No universal Java management foundation exists yet. The
previous JMAPI draft has not reached the Specification stage
and does not address the following market requirements:
+ Integration of the new trends for third generation
Web-based distributed management.
+ Leveraging of up-to-date Java technology like JavaBeans
and Jini.
+ Integration with legacy or non-Java environments (such
as SNMP and CIM/WBEM).
- Specification to be developed
JMAPI 2.0 will provide a management architecture, APIs and
services for building Web-based, distributed, dynamic and
modular solutions to manage Java enabled resources.
The JMAPI architecture will be applicable to the creation of
smart Java agents and management applications, and can also be
integrated into legacy management solutions.
JMAPI 2.0 will strongly leverage an existing product, and
hence should lead in the short term to a mature Specification
and to the availability of a commercial implementation.
- Underlying technologies
The JMAPI Specification will leverage the Java Dynamic
Management Kit technology. This product provides a core
management framework which is a repository of Java Management
Beans. Basically any Java bean can be registered in the
framework and then expose management capabilities.
Management operations can be performed either:
+ locally, from the same VM, or
+ from a remote VM, or
+ from a remote non-Java management application or
browser.
This product also provides a set of core distributed
management services that can be deployed in manager, agent or
agent/manager applications.
- Proposed package names
JMAPI APIs and services will be divided into:
+ a set of mandatory services, which any conformant
implementation will be required to implement.
We propose to group all these services under the
following package name:
javax.management.core
+ a set of optional services, which any conformant
implementation might choose or not to implement.
We propose to define each of these services as a package
named after the following scheme:
javax.management.
Section 3: Contributions
- Existing documents, specifications, implementations &
How they might be used
+ "Java Dynamic Management Kit - A white paper"
+ "Java Dynamic Management Kit 3.0 Programming guide"
These two documents can be leveraged as a description of the
concepts and architecture of the underlying technology, as
well as a description of the core management services.
+ "Java Dynamic Management Kit 3.0 Reference Manual"
This document can be used as a initial input to the
definition of the APIs.
+ "Java Dynamic Management Kit 3.0"
The product implementation will be leveraged to deliver the
reference implementation. The next major release of the
product will be JMAPI compliant and will provide a first
commercial implementation of the Specification.
+ The test suite of Java Dynamic Management Kit 3.0 will be
leveraged to deliver the Compatibility Test Suite.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
