A.1 JMX Agent Implementations

A.1.1 JMX 1.0 Reference Implementation from Sun Microsystems

Version 1.0 of the JMX reference implementation was released in December 2000. The reference implementation source [2] is licensed under the Sun Community Source License (SCSL). According to the Free Software Foundation (http://www.gnu.org/philosophy/license-list.html#SunCommunitySourceLicense) and numerous editorials at the time of the SCSL release, this license is not well thought of in the free-software and open -source communities. The reference implementation binary is available for free.

JMX 1.1, a maintenance release, is available from the same Web site. For more information and access to the source or binary versions of the reference implementation, see http://java.sun.com/products/JavaManagement.

Sun also provides a Web site called the JMXperience at http://java.sun.com/products/JavaManagement/JMXperience.html, where Sun and other vendors can contribute interesting tools, MBeans, and components for JMX. Sun has contributed a remoting component that provides a remote MBeanServer for use by JMX clients (usually JMX managers) and an Mof2MBean tool that generates MBean skeletons from CIM MOF files.

A.1.2 JDMK 4.2 from Sun Microsystems

JDMK 4.2 [3] was released in 2001. It is the only JMX-compliant implementation (having passed the TCK that Sun developed). You must purchase this product from Sun. It contains adapters for HTTP, RMI, and SNMP. The SNMP adapter works only for MBeans generated from SNMP MIBs by JDMK's MIBGen tool. The adapter does not support the "random" MBean. The SNMP adapter supports SNMP versions 1 and 2. JDMK provides a remote-manager component that includes a proxy for the MBeanServer, and proxies for the MBeans, to make the development of JMX managers easier. It also provides a JMX manager and tools to help define and manage the MBeans. For more information, see http://www.sun.com/software/java-dynamic.

A.1.3 TMX4J 1.0 from Tivoli Systems

TMX4J 1.0 [4] was released in February 2001. It is a cleanroom implementation of the JMX specification, and it is JMX compatible, not compliant. It is available from IBM's alphaWorks Web site at http://alphaworks.ibm.comtech/TMX4J. The licensing on this software is the standard alphaWorks trial license. However, alphaWorks is now making technologies available for release by products on a per-technology basis. More information is available at http://www.alphaworks.ibm.com/license. TMX4J contains an HTTP and RMI adapter, and support for a logging facility with JLog. [5] It also comes with a very nice tutorial. IBM's products that support JMX use TMX4J, including WebSphere 5.0, [6] WebSphere Voice Server, [7] WebSphere Edge Server, [8] WebSphere Business Integrator, [9] WebSphere Business Components Composer, [10] and Tivoli Web Component Manager. [11]

A.1.4 AdventNet Agent Toolkit Java/JMX Edition [12]

AdventNet [13] was the first vendor to ship a product with JMX support. Its management agent toolkit supported the JMX 0.8 version before the JMX specification was final. The most recent version has passed the JMX TCK and is now fully JMX compliant. You must purchase this product from AdventNet. This toolkit includes a rapid prototyping and development tool for building JMX agents, and it includes adapters for SNMP, HTML, RMI, HTTP, CORBA, and TL1 (Transaction Language 1). It also supports distributed JMX agents in a gateway or cascading configuration, as well as the building of stand-alone SNMP and TL1 agents in Java. You can get more information at http://www.adventnet.com/products/manageengine/index.html. Other AdventNet products that use JMX are ManageEngine and Web NMS.

A.1.5 AdventNet ManageEngine

AdventNet ManageEngine is a graphical development environment that helps developers expose business- or application-specific management information even after an application is developed and deployed. JMS (Java Message Service) and Web service JMX adapters are also being supported to integrate the management infrastructure with the existing middleware infrastructure. For more information, see http://www.adventnet.com/products/manageengine/index.html.

A.1.6 MX4J

MX4J [14] is an open-source implementation release of the JMX 1.0 specification that is JMX compatible because it has not passed the JMX TCK. This is understandable, given the current licensing arrangements for the TCK. MX4J uses the Apache [15] licensing model. It provides an HTTP, RMI-over-JRMP, [16] and RMI-over-IIOP adapter. It also includes a tool that allows you to generate your MBean interface via XDoclet. Another interesting extension of MX4J is dynamic proxy support for MBeans so that the calls to the MBeans in your programs are more intuitive. The MX4J implementation has a logging facility that makes it fairly easy to redirect the data to another logging facility, such as log4j. [17] MX4J provides some additional service MBeans: a naming MBean that wraps the RMI registry, a mailer MBean that sends e-mail, and a JythonRunner MBean that runs Jython scripts. You can find more information at http://mx4j. sourceforge .net.



Java and JMX. Building Manageable Systems
Javaв„ў and JMX: Building Manageable Systems
ISBN: 0672324083
EAN: 2147483647
Year: 2000
Pages: 115

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net