State Monitoring 

Use

Monitoring the J2EE Engine activity is a critical point in the administration process. The J2EE Engine provides a JMX™ compliant monitoring infrastructure that enables different resources to register as providers of monitoring data. This infrastructure uses MBeans to represent both J2EE Engine resources and the resources of deployed applications. Options are provided to monitor the actual state, to keep a history and to react to critical situations using an alert mechanism. The use of the JMX protocol ensures that external tools can access the monitoring data.

In order to collect monitoring data at runtime, this data can be either pulled periodically by a JMX™ monitor from the underlying resource (passive instrumentation) or alternatively the resource pushes the monitoring data to the JMX™ monitor using an event mechanism (active instrumentation).

The monitoring framework uses XML-based configuration files as a source for creating new monitors, objects and summaries. Both static and dynamic monitors can be defined in this XML file.

The JMX™ monitors use corresponding monitor nodes for storing monitoring data. Depending on the monitoring data type, you can choose JMX™ monitors and corresponding monitor nodes for text information, integer numbers or more complex data such as tables and frequencies. The logic of the monitor nodes allows them to accumulate data, keep a history or generate alerts when a critical state has occurred.

The state of the engine and of the applications can be displayed both in the Visual Administrator and in the CCMS (if you have a CCMS agent and you have activated the reporting of data). For more information, see State Monitoring in the Visual Administrator and State Monitoring of the J2EE Engine Using CCMS.