| ILOG JRules User Guide > Managing Rule Execution Server > Getting Started > Overview: Rule Execution Server Management |
Overview: Rule Execution Server Management |
PREVIOUS NEXT |
Rule Execution Server provides an environment for you to manage the execution of your rules on both the J2SE and J2EE platforms. Rule Execution Server includes a set of management facilities that allow System Administrators to change the behavior of the execution stack, and disable rulesets in emergency situations.
JRules provides a number of ways to deploy and retrieve rulesets from the Rule Execution Server infrastructure. Apache Ant and JMX are used to automate deployment; see Managing RuleApps Using the MBeans Accessor API.
The following figure shows the different tools that are provided to push the rulesets from your development environment to Rule Execution Server. RuleApp archives provide a means to prepare your rules for deployment. Rule Execution Server can manage the archive from the meta information that is provided in the RuleApp descriptor.
The figure also shows the mechanisms to retrieve RuleApps deployed on Rule Execution Server. An archive can be retrieved for each RuleApp deployed on the server, or a single archive can be created that contains all the RuleApps deployed on Rule Execution Server.
Having installed and tested the execution of your rules on Rule Execution Server, it may become clear that the default behavior of the execution stack requires some adjustment. There are a number of properties that you can change within the specific deployment descriptor of the Execution Unit (XU) to address specific execution needs.
This section describes how you can adjust the execution stack and how you can monitor the performance and the managerial events inside Rule Execution Server. It also covers tasks such as registering a decision service and using the management model API.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |