OneSight Administrator Guide

Configuring JMX Monitors
about the success or failure of the test and indicates what may
be causing any problem.
18. If the test succeeds, click OK in the Add Monitor dialog box to
save these basic OneSight Voice Transaction Profile monitor
settings. You can now add this monitor to a monitor group.
Refer to Adding Monitors to a Monitor Group in Chapter 4.
Configuring JMX Monitors
The JMX monitor lets you determine if a Java application is
performing properly. The JMX monitor checks the specified JMX
MBean Attribute values at specified time intervals to confirm that
the Java application is performing as expected. The JMX monitor
also provides an easy way to confirm whether or not the JMX
application is running.
The JMX monitor connects to the remote JMX application’s MBean
Server using Java RMI protocol for Weblogic and JBoss and SOAP
for WebSphere. Once connected to the MBean Server, the JMX
monitor can get an MBean’s Attribute’s current value. The JMX
monitor configuration can also discover all available MBeans that
the MBean Server knows about, making it easy to select the name
of the MBean and its attribute of interest.
For the JMX monitor to be able to connect to an MBean Server, the
JMX-enabled application’s jar file must be copied to the monitoring
(Data Collector) machine in a default directory location as specified
in the table below. The jar file on the Data Collector machine must
be the same version (that is, an exact copy) of the jar file that the
JMX application is using, otherwise, the JMX monitor will not be
able to connect to that MBean Server.
The JMX monitor can concurrently connect to any number of
MBean Servers and versions with some exceptions as described in
―Installing the Data Collector on a Windows Machine,‖ in
Chapter2. During the data collector installation process, you must
have selected the application server(s) that you are using. If the
Chapter 5: Configuring Monitors 215