JMX (Java Management Extensions)

Top Previous Next

The JMX Device Driver allows AggreGate Server to communicate with Java-based applications and Application Servers using Java Management Extensions (JMX) protocol. Functionality provided by the driver:

•	Discovery of MBeans provided by an MBean Server (JMX host).

•	Creation of a Device context setting per every avilable MBean attribute.

•	Creation of a Device context operation per every operation provided by MBean.

•	Creation of a Device context event definition per every notification type provided by MBean.

Driver Information

Driver Plugin ID:

com.tibbo.linkserver.plugin.device.jmx

Global Settings

None defined.

User Level Settings

None defined.

Device Properties

Connection Properties

Connection properties define how AggreGate Server communicates with a JMX server. These settings may be accessed using the Edit Device Properties action of Device Context. The following connection properties are available:

Property	Description
Host	IP address of host name to connect to.
Port	Port to connect to.
Username	Username to use for authentication.
Password	Password to use for authentication.
Ignore Attributes Producing Read Errors	If enabled, no setting variables will be created for the MBean attbitutes that has generated read errors during MBean meta-data analysis (e.g. first attribute read attempt).

Device Assets

The driver creates one root asset for every MBean instance provided by the MBean server.

Device Settings

JMX device driver creates one Device setting variable per every attribute of every discovered MBean. These variables are grouped by MBean names and/or descriptions to facilitate navigation.

Device Operations

JMX device driver creates one Device context function and action per every operation provided by every discovered MBean. These actions are grouped by MBean names and/or descriptions to facilitate navigation.

Device Events

JMX device driver creates one Device context event definition per every notification type of every discovered MBean. The driver automatically adds a notification listener for every notification and generates a AggreGate Server event when a notification is received.

Connection Handling

This driver makes the device Online if:

•	TCP connection to a JMX host was successfully established

•	JMX RMI connector authentication and authorization did not fail

Synchronization Details

Synchronization between AggreGate Server and JMX host includes the following steps:

•	Reading a list of available MBeans.

•	Reading information about attributes provided by every MBean.

•	Reading information about operation provided by every MBean.

•	Reading information about notifications provided by every MBean.

•	Reading/writing values of all attributes.

•	Subscribing to the notifications.