Monitoring Ruleset Execution Using the MBeans Accessor API

ILOG JRules User Guide > Executing Rules > Tasks > Executing a Ruleset Using Rule Execution Server > Monitoring Ruleset Execution Using the MBeans Accessor API

Monitoring Ruleset Execution Using the MBeans Accessor API

The IlrJmxRulesetMBean interface shows all the execution metrics available on each ruleset MBean.

To monitor ruleset execution using the MBeans Accessor API:

Connect your JMX client to the MBean server of the application server.
Access the ruleset MBean from the interface.
Invoke the get methods that you want.

The results are shown in your JMX tool.

The following table lists the IlrJmxRulesetMBean methods

Table 1 IlrJmxRulesetMBean Methods

Type	Method Name	Type	Method Name
`long`	`getAverageExecuteTaskTime()`	`long`	`getAverageExecuteTime()`
`long`	`getExecuteTaskCount()`	`long`	`getExecuteCount()`
`long`	`getFirstExecuteTaskTime()`	`long`	`getFirstExecuteTime()`
`long`	`getLastExecuteTaskTime()`	`long`	`getLastExecuteTime()`
`long`	`getMaxExecuteTaskTime()`	`long`	`getMaxExecuteTime()`
`long`	`getMinExecuteTaskTime()`	`long`	`getMinExecuteTime()`
`long`	`getTotalExecuteTaskTime()`	`long`	`getTotalExecuteTime()`

Related Concepts

Ruleset Execution Trace

Related Tasks

Creating a POJO Client Project for RuleApps

Creating a Web Service or Monitored Transparent Decision Service Project for RuleApps

Creating an SCA Component Client Project for RuleApps

Adding RuleApp Execution Artifacts to an Existing Project

Maintaining Execution Code Generators

Implementing a Ruleset Execution Interceptor

Invoking a Ruleset Using a Stateless Rule Session

Invoking a Ruleset Using a Stateful Rule Session

Invoking a Ruleset Using a Message-Driven Rule Bean

Tracing Ruleset Execution

Handling Rule Engine Exceptions in Rule Execution Server

Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage.