Printed: Apr 24, 2014
From: http://www.jcp.org/en/jsr/detail?id=77

Standard Format


Community
Expert Group

Summary  |  Proposal  |  Detail (Summary & Proposal)
JSRs: Java Specification Requests
JSR 77: J2EETM Management

Stage Access Start Finish
Maintenance Release Download page 22 Jun, 2006  
Maintenance Draft Review Download page 25 Aug, 2005 26 Sep, 2005
Final Release Download page 19 Jul, 2002  
Final Approval Ballot View results 23 Apr, 2002 06 May, 2002
Proposed Final Draft 2 Download page 21 Mar, 2002  
Proposed Final Draft Download page 25 Feb, 2002  
Public Review Download page 19 Dec, 2001 18 Jan, 2002
Community Draft Ballot View results 28 Aug, 2001 04 Sep, 2001
Community Review Login page 30 Jul, 2001 04 Sep, 2001
Expert Group Formation   22 Aug, 2000 01 Sep, 2000
JSR Review Ballot View results 08 Aug, 2000 21 Aug, 2000
Status: Maintenance
JCP version in use: 2.6
Java Specification Participation Agreement version in use: 2.0


Description:
The JavaTM 2 Platform, Enterprise Edition Management Specification will provide server vendors and tool vendors with a standard model for managing the J2EE Platform.

Please direct comments on this JSR to the Spec Lead(s)
Team

Specification Leads
  Hans Hrasna Oracle
Expert Group
  BEA Systems Borland Software Corporation Flashine.com
  IBM/Websphere Informix Software Laminar Software
  Lutris Technologies Opnet Technologies, Inc Oracle
  Pramati Technologies Progress Software Sitraka

Updates to the Java Specification Request (JSR)

The following has been updated from the original JSR:

This JSR was originally developed under JCP 2.1, and moved to JCP 2.6 as part of the Maintenance process.

2.11 Please describe the anticipated schedule for the development of this specification.

The tentative schedule is as follows:

Milestone Date
Community Draft May 2001
Public Draft August 2001
Proposed Final Draft October 2001
Final Release Aligned with J2EETM 1.4 Platform Spec Final Release

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Title:

Java 2 Platform, Enterprise Edition Management Specification

Summary:

The Java 2 Platform, Enterprise Edition Management Specification will provide server vendors and tool vendors with a standard model for managing the J2EE Platform.

Section 1. Identification

Submitting Member: Sun Microsystems, Inc.

Name of Contact Person: Hans Hrasna

E-Mail Address: hans.hrasna@sun.com

Telephone Number: (781) 442-0231

Fax Number: (781) 442-1610


Specification Lead: Hans Hrasna

E-Mail Address: hans.hrasna@sun.com

Telephone Number: (781) 442-0231

Fax Number: (781) 442-1610


Initial Expert Group Membership:



Section 2: Request

2.1 Please describe the proposed Specification:

The Specification proposes a standard management model for exposing and accessing the management information, operations, and parameters of the Java 2 Platform, Enterprise Edition components. The management model will:

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Java 2 Platform, Enterprise Edition

2.3 What need of the Java community will be addressed by the proposed specification?

As the installed base for J2EE platforms and J2EE applications grows, the need for management tools is becoming increasingly apparent. In order to be effective, J2EE management tools need the ability to transparently manage a network of multiple J2EE servers, which could consist of multiple vendor implementations of the platform. The current selection of J2EE management tools are implementation-specific and weaken the platform in the area of distributed management.

The specification will address application-independent management functions on the Java 2 Platform, Enterprise Edition. Application-independent management functions will be specified for two major categories:

Java 2 Platform, Enterprise Edition Management will be defined using standard management information formats and protocols, such as JMX, WBEM, and SNMP, in such a way as to provide information that can be managed by standard system management applications.

2.4 Why isn't this need met by existing specifications?

The Java 2 Platform, Enterprise Edition Specification does not address the issues of resource monitoring or management of J2EE components: application clients, EJBs, servlets, or JSPs.

2.5 Please give a short description of the underlying technology or technologies:

One way an application server could implement the requirements this JSR will specify is through the use of JMX technology. JMX defines a management architecture, APIs, and management services. It provides developers of Java technology based applications with the means to instrument Java platform code, create smart agents and managers in the Java programming language, implement distributed management middleware, and smoothly integrate these solutions into existing management systems. In addition, JMX provides a number of Java APIs for existing standard management protocols. These APIs enable JMX applications in the Java programming language to link with existing management technologies, including WBEM and SNMP.

Web-Based Enterprise Management (WBEM) is a set of management and Internet standard technologies developed to unify the management of enterprise computing environments. WBEM is made up of a core set of standards, which includes a data model, the Common Information Model (CIM) standard; an encoding specification, xmlCIM Encoding Specification; and a transport mechanism, CIM Operations over HTTP.

SNMP is the most basic, but also the most widely implemented of the management standards. Its support provides minimal management and monitoring capabilities through a variety of existing management tools.

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

Not applicable.

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?

The current J2EE security model does not address security issues related to management functions. We will extend the J2EE security model to cover these issues in a way that is compatible with the standard protocols that will be used.

2.9 Are there any internationalization or localization issues?

No. The Java 2 Platform, Enterprise Edition Management Specification will use the I18N and L10N support in the Java 2 Platform, Standard Edition.

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

This JSR is expected to affect the next J2EE platform specification (after 1.3).

2.11 Please describe the anticipated schedule for the development of this specification.

The tentative schedule is as follows:

Community Draft July 2001
Public Draft November 2001
Proposed Final Draft February 2002
Milestone Date

This information has been updated from the original JSR.

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.

Java 2 Platform, Enterprise Edition 1.2
http://java.sun.com/products/j2ee/docs.html

Java Servlet Specification, Version 2.2
http://java.sun.com/products/servlet

Java Management Extensions Instrumentation and Agent Specification, v1.0
http://java.sun.com/products/JavaManagement

Java Management Extensions CIM/WBEM APIs, Draft 2

Java Management Extensions SNMP APIs, Draft 2

Java WBEM Services APIs, Draft 1

3.2 Explanation of how these items might be used as a starting point for the work.

Four of the specifications (Java Management Extensions, Java WBEM Services, Java Management Extensions CIM/WBEM, and Java Management Extensions SNMP) provide problem space modeling strategies of which this specification can make use.

We expect to take advantage of the experience gained from a number of projects, including several represented by the specifications above.