Monday, October 28, 2002 01:22 AM
First of all, JMX is a Java specific application architecture for allowing vendor independant management of server applications. SNMP is a platform neutral protocol for accessing management information over TCP/IP. And finally, Tivoli is a software product.
Other than existing for the same purpose, there is no relation between JMX and SNMP. However, it is entirely possible that an application exposing some JMX manageable components would also expose some information about these components via SNMP. The reason being that at this point in time, SNMP is supported by many management UIs, and that JMX is only starting to pick up momentum.
JMX is interesting as it actually offers more than a simple management protocol. It is actually an application architecture. The spec defines some interfaces, as well as some very specific software entities. It also recommends that the management capabilities be divided into components, each exposing some properties and methods. It is very natural to extend this component design to the business side of the application. A good example of the influence of JMX on the overall structure of an application is JBoss. The application server is built around its JMX core, and each of the entities exposed via the management interface is actually an independant server component loaded automatically by the JMX core. SNMP on the other hand does not provide any similar recommendations or requirements on the architecture of the managed application.
hope that helps