Find JSRs
Submit this Search

Ad Banner

JSRs: Java Specification Requests
JSR 71: JMX-TMN Specification

This JSR has been Withdrawn
Reason: Withdrawn at the request of the Specification Lead.

Update to the Specification

Due to the change in Specification Lead, the following change has been made to the original specification.

Name of Proposed Spec Lead: Aline Ellul

Spec Lead E-Mail Address:

Spec Lead Telephone Number: +33 1 30 80 69 54

Spec Lead Fax Number: +33 1 30 80 78 50

Original Java Specification Request (JSR)

Identification | Request | Contributions

Section 1. Identification

Submitting Participant: Bull S.A. (BullSoft)

Name of Contact Person: Philippe Roy

Contact E-Mail Address:

Contact Telephone Number: +33 (1) 30807211

Contact Fax Number: +33 (1) 30803346

Name of Proposed Spec Lead: Philippe Roy

Spec Lead E-Mail Address:

Spec Lead Telephone Number: +33 (1) 30807211

Spec Lead Fax Number: +33 (1) 30803346

(NOTE that this information has been updated since the original.)

Initial Expert Group Membership:

Bull S.A. (BullSoft)


Schmid Telecom

Section 2: Request

2.1 Please describe the proposed Specification:

JMX-TMN specification is part of the second phase of the Java Management Extensions (JMX) umbrella initiative.

Telecommunication Management Network (TMN) is a public standard, widely deployed for telecommunication networks. It was created to aid administrators in managing their services, networks and the network elements that make up the network.

Java Management Extensions (JMX) is a set of specifications and APIs for application and network management all under a single umbrella specification.

The JMX Instrumentation is the optional package to the J2SE platform, that defines how Java-based or Java-enabled resources should be made manageable.

The JMX Agent specification is the optional package to the J2SE platform that defines how JMX resources instrumented in compliance with JMX Instrumentation, can be seen and used by Java-based management systems and applications.

There is a requirement on the market to integrate TMN-based and JMX-based management systems, in both directions. Having JMX compliant resources being managed by existing TMN-based management with underlying CMIP/CMISE management paradigms platforms, systems and applications. And also having JMX-based management systems being able to manage existing CMIP/CMISE compliant resources.

In its first phase (JSR 000003) JMX identified this need for TMN support, but postponed the definition of Java APIs for TMN managers.

The intent of this JMX-TMN specification is to define a set of APIs and procedures to make a JMX application TMN enabled, either as a TMN manager or TMN agent. This will allow JMX to manage a TMN environment and allow parts of JMX agents to be managed by TMN managers.

The JMX-TMN specification will not become an optional package to any Java platform, since it does not intend to extend the capabilities of Java platforms.

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

Any Platform with a J2SE Java Virtual Machine

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

This specification will allow Java developers to smoothly migrate from TMN to JMX and to progressively integrate Java enhancements into TMN management systems. The Java Management Extension (JMX) Specification (JSR-000003) is defining a standard for instrumenting Java resources (JMX Instrumentation for making them manageable in a standard and universal manner) and exposing their management properties to Java-based management solutions (JMX Agent). Because TMN technology is widely deployed in the telecommunications industry, this specification will define how to get JMX and TMN environment interact.

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

In its first phase (JSR000003) JMX identified this need for TMN support, but did not address it. This specification will focus solely on the integration between JMX and TMN domains.

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

The tools and APIs in this specification will allow developers to create JMX applications that can manage TMN agents and/or services (JMX-TMN Manager) and/or be managed by TMN managers (JMX-TMN Agent).

JMX-TMN Manager

  • Two sets of Java classes used to simplify the development of applications used to manage TMN agents and services. These classes will allow an application to retrieve information from TMN agents and also receive event notifications from the agents.
  • low level CMISE-like API
  • high level Managed Object API
  • A set of Java classes comprising a TMN Alarm Service. These classes will allow an application to retrieve alarm information, dynamically receive alarms and acknowledge/clear alarms.


  • A set of Java classes that will allow a JMX application to be managed by an TMN manager. These classes will give the developer the ability to listen for TMN requests, implement security on these requests and send TMN event notifications to managers.
  • Documents and tools to map JMX Management Beans to MIT (Management Information Tree) objects. The Management Interfaces of the JMX application Managed Beans are analyzed and used - under user input control, to derive a ITU-T compliant MIT (X721, M.3100, etc). This MIT will enable TMN Management Consoles to access and manage the application's Beans. A mapping document will define how and under which restrictions JMX Management Beans will be made accessible to an TMN Management Console. This document will focus on
  • Defining a set of mapping rules to map MBeans on MIT conceptual objects
  • Defining under which restrictions Managed Beans, attributes of Managed Beans and actions defined on Managed Beans can be accessed/triggered through TMN.

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

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

It is only dependent on a Java Virtual Machine being present.

2.8 Are there any security issues that cannot be addressed by the current security model?


2.9 Are there any internationalization or localization issues?


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

None. We will work within the JMX umbrella to provide integration with JMX (JSR-000003) specification.

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

We plan a participant draft before end 2000.

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.

The TMN standard has been defined by ITU-T ( in the M.3000 recommendation and subsequent recommendations. These recommendations can be bought from ITU-T web site.

The JMX JSR can be found at

Dyade (, has implemented a JMX compliant TMN infrastructure, this JSR intends to reuse this development.

Sun Solstice Enterprise Manager 3.0 ( has implemented a Java Managed Object API based upon the TMN C++ Green API, and a Java Alarm Service API based upon ITU-T X.721, X.733. This JSR intends to reuse these components.

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

The TMN standards are widely implemented and deployed on the market.

The First Public Release of JMX-TMN Manager API will give you a good understanding of how a developer can create a TMN Manager using Java code.

The JMX Instrumentation and JMX Agent specification define the architecture for Java-based management systems.

We'll contribute our expertise to develop similar specifications for the other APIs and tools needed to provide a complete integration between TMN technology and JMX Instrumentation and JMX Agent technologies.