 
Use of JCP site is subject to the
JCP Terms of Use and the
Oracle Privacy Policy
 |
|
 JSRs: Java Specification Requests
JSR 146: WBEM Services: JMX Provider Protocol Adapter
Reason: After a year and a half of no progress, the Spec Lead suggested withdrawing the JSR and the Expert Group did not object. JCP version in use: 2.1 Java Specification Participation Agreement version in use: 1.0 Description: JSR-048 defines WBEM support for Java. This specification would have defined how JMX instrumentation mapped to CIM and the definition of a JMX Provider Protocol Adapter for WBEM Services. Please direct comments on this JSR to the Spec Lead(s) Team
This JSR has been Withdrawn
Identification |
Request |
Contributions
Original Summary: WBEM Services (JSR-048) is the specification that defines the architecture and API for WBEM support for Java. This specification will define how JMX instrumentation can be mapped to CIM and the definition of a JMX Provider Protocol Adapter for WBEM Services. Section 1. Identification Submitting Member: Sun Microsystems, Inc. Name of Contact Person: Jim Davis E-Mail Address: james.d.davis@sun.com Telephone Number: +1 781 442 2755 Fax Number: +1 781 442 1651 Specification Lead: Jim Davis E-Mail Address: james.d.davis@sun.com Telephone Number: +1 781 442 2755 Fax Number: +1 781 442 1651 Initial Expert Group Membership: Sun Microsystems, Inc. Section 2: Request
2.1 Please describe the proposed Specification:This specification will produce the following: (1) A specification describing how to map JMX instrumentation to CIM CIM (Common Information Model) is a common data model of an implementation-neutral schema for describing overall management information in a network/enterprise environment. CIM is comprised of a Specification and a Schema. The Specification defines the details for integration with other management models (i.e., SNMP's MIBs or the DMTF's MIFs), while the Schema provides the actual model descriptions. The mapping algorithm will be determined by the expert group. It is not yet known whether this will be a generic mapping or if there will be design patterns required for developing with JMX when wanting to integrate within a WBEM environment. This will be determined by the expert group. (2) A specification for a WBEM Services Provider Protocol Adapter for JMX A provider protocol adapter provides the adaption of one protocol or object model to the CIM object model so that it can interoperate or integrate into a WBEM environment. Examples of provider protocol adapters include, but are not limited to, SNMP, CMIP, TMN, and of course JMX. The WBEM Services provider protocol adapter will be developed using the WBEM Services (JSR-048) and JMX (JSR-03) APIs. 2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)All 2.3 What need of the Java community will be addressed by the proposed specification?This specification will address how JMX (JSR-03) instrumentation can be accessed through WBEM (JSR-48). This specification allows existing JMX instrumentation to be accessible in a WBEM environment. 2.4 Why isn't this need met by existing specifications?JMX specifies a way to instrument information in Java. JMX is protocol and object model independent. WBEM Services describes an architecture that allows multiple instrumentation technologies, multiple protocols, but one object model. This specification will build on JMX and WBEM Services by defining how JMX instrumentation will work in a WBEM environment. Since the WBEM Services specification has protocol definitions, there will be a standard way to access JMX instrumentation. 2.5 Please give a short description of the underlying technology or technologies:This specification will build on the WBEM Services JSR (JSR-48) and the JMX JSR (JSR-03). 2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)TBD by the EG 2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?No 2.8 Are there any security issues that cannot be addressed by the current security model?No 2.9 Are there any internationalization or localization issues?No 2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?No. This specification will build on JSR-48 and JSR-03. 2.11 Please describe the anticipated schedule for the development of this specification.We hope to complete the specification, RI and TCK within 9 months of the JSR acceptance. 2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.The Expert Group (EG) will be formed following JSR acceptance. The EG will work via biweekly conference calls, email, and face to face meetings. Section 3: Contributions
3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.JSR-48 Specification
JSR-03 Specification 3.2 Explanation of how these items might be used as a starting point for the work.This JSR will use the WBEM Services JSR and JMX JSR as a starting point by building upon the existing reference implementations or having a dependency on these reference implementations. |
|||||||||||||||||||||||||||||||||||||||
