This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
JMX is not a program - it is an API that allows you to monitor a (possibly remote) application and (optionally) change its behavior at runtime. Incorporating JMX means to define which aspects of an application can be monitored/controlled -by defining in interface-, and enabling JMX access in the application. Then you can use any of a number of JMX monitoring tools to access your application through that interface.
Originally posted by vinayaga moorthi: hello friends,
i need the details of "how to run the JMX program" and what are the rewuirements for running the JMX programs. help me. i am doing project on this concept.
To run a "JMX program", you need a JMX container. Java 5 has one built into the JVM. Tomcat, Weblogic, Websphere, etc. all have JMX containers built in. These containers have programs (known as mbeans) which report the status of the application that it is monitoring.
For example, in the Weblogic JMX container, there is an mbean for each servlet, EJB, user connection, etc., in the system. You can connect to the JMX container, either through JNDI, or via a connector, find the mbean you want, and monitor or control the item that the mbean is managing.
Another example, if you have an EJB with special management needs that you want to expose. You can write an mbean, which can be loaded into the JMX container. This mbean will take management requests from clients -- and internally, will make a JNDI connection to your EJB, working through a private (not documented) interface.