Introduction to MQe JMX

The Java™ Management Extensions (also called the JMX specification) define an architecture, the design patterns, the APIs, and the services for application and network management in the Java programming language. The JMX specification provides Java developers across all industries with the means to instrument Java code, create smart Java agents, implement distributed management middleware and managers, and smoothly integrate these solutions into existing management systems.

The JMX architecture provides the following benefits:
  • Enables Java applications to be managed without heavy investment

    A Java application simply needs to embed a managed object server and make some of its functionality available as one or several Manageable Beans registered in the object server; that is all it takes to benefit from the management infrastructure.

  • Provides a scalable management architecture

    Every JMX agent service is an independent module that can be plugged into the management agent, depending on the requirements. This component-based approach means that JMX solutions can scale from small footprint devices to large telecommunications switches and beyond.

  • Integrates existing management solutions

    JMX smart agents are capable of being managed through HTML browsers or by various management protocols such as SNMP and WBEM. The JMX APIs are open interfaces that any management system vendor can leverage.

  • Can leverage future management concepts

    The APIs of the JMX specification can implement flexible and dynamic management solutions through the Java programming language which can leverage emerging technologies.

    The goal of the JMX API for MQe is to provide a JMX instrumentation level for MQe resources (queue managers, queues, and so on). The instrumentation is designed to have a small footprint, and to be flexible, easy to use and JMX compliant.

  • Small footprint

    The JMX API for MQe and the JMX implementation minimize resource demands in terms of size and memory requirements.

  • Flexible

    The implementation is modular so that MQe developers can choose to use the API when manageability is desired and the overhead of the JMX implementation is within the capabilities of their target platforms. Or they can choose to leave it out without incurring any memory or performance penalty.

  • Easy to use

    The API is simple and easy to use: it is possible to enable an existing MQe application for JMX with only a few lines of code.

  • JMX compliant
    JMX compliance is virtually guaranteed by using the reference implementation developed by Sun Microsystems. From JMX v.1.2 onwards, open MBeans are a mandatory part of any JMX implementation, so we adhere to the data types required for open MBean instrumentation. Thus, all operation parameters and attributes are of the following data types:
    • Simple data types:
      • java.lang.Void
      • java.lang.Boolean
      • java.lang.Byte
      • java.lang.Character
      • java.lang.String
      • java.lang.Short
      • java.lang.Integer
      • java.lang.Long
      • java.lang.Float
      • java.lang.Double
    • Arrays of the above types:
      • javax.management.ObjectName
      • javax.management.openmbean.CompositeData
      • javax.management.openmbean.TabularData

Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.