|
|
[ Index ] [ Individual Project ] [ Placement Presentation ] [ Timetable ]
[ Index ] [ Research ] [ Schedule ]
Being a white paper it was aimmed at a different audience than myself. It didn't contain anything technical but was useful as an overview of JMX. A lot of the information can also be found in the JMX Specification.
The paper starts off saying that current static management systems do not meet today's needs since they need knowledge of all resources in advance, therefore to manage new services the implementation must be updated. The problem being that new services are being created faster than the implementation can be updated. There would be no benefit in recreating static management systems in Java, we need a dynamic management extension, enter JMX.
JMX defines an management architecture, APIs, and management services all under a single umbrella specification. JMX was developed by Sun along with other leaders in the management field, and it is following the Java Community Process.
JMX is divided into three layers:
As we move from a client-server model to a service driven network we need a way to manage the network, and in turn the management system needs to be flexible, just like JMX.
JMX is lightweight and it doesn't take a lot of code to instrument existing code. This allows developers to focus on the core product rather than management. In addition the instruments can then be used by an JMX compliant agent.