| ILOG JRules User Guide > Managing Rule Execution Server > Concepts > Rule Execution Server Management Model |
Rule Execution Server Management Model |
PREVIOUS NEXT |
The Rule Execution Server management model is implemented as a set of JMX Management Beans (MBeans), which are deployed to the MBean server. All operations that can be performed using the Rule Execution Server Console can be exposed as JMX Bean methods.
The Rule Execution Server JMX infrastructure provides a standard way to deploy, manage, and monitor Rule Team Server's execution resources. The various Rule Execution Server model MBeans are the runtime proxies on each entity of the Rule Execution Server model.
The IlrJmxModelMBean is the root of the Rule Execution Server management model. It controls every RuleApp deployed on Rule Execution Server. This MBean performs actions such as adding and removing references to the RuleApps contained within the model.
The IlrJmxRuleAppMBean is a management entity that controls a deployed RuleApp on Rule Execution Server. This MBean performs actions such as adding and removing references to the rulesets contained within a RuleApp.
The IlrJmxRulesetMBean is the management entity that represents the execution resources for the Execution Unit (XU). This MBean exposes some runtime metrics of the execution. These metrics are computed from the various data collected on each XU in a cluster. It exposes an API to set the resources and properties that are used at execution time and provides a "hot" deployment entry point to update the rules in a running Rule Execution Server.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |