Adding a JMX-based Test
Most enterprises have custom developed application components running directly on the JVM directly or hosted on standard, off-the-shelf middleware application servers (such as WebLogic, WebSphere, JBoss, etc.). While monitoring the JVM or the web application servers provides visibility into the core engines that support the Java applications, it does not provide any information on the custom application components. Java Management eXtensions (JMX) offers a standard way by which applications can expose custom metrics for monitoring tools. Many custom applications use JMX to publish information about their functioning to third party monitoring applications.
The eG Integration Console has now been enhanced to collect and report on applications that offer JMX-based interfaces. Administrators now have a new Jmx option, using which they can specify the specific JMX attributes that the eG agents must collect to monitor their custom applications. Administrators can specify the JMX attribute name and the specific MBeans to be monitored, and the eG agent takes care of periodically polling these attributes and reporting the metrics back to the eG Enterprise console. This capability offers administrators a quick and easy way to integrate monitoring of their custom Java applications into the enterprise management console.
This section takes the help of an example to help you understand how a test of type JMX can be built. The JMX test to be added for this purpose will be connecting to a custom Java application and reporting the following to indicate how the JVM of that application uses its heap memory.