Rule Execution Server basics

The Rule Execution Server architecture is based on components.

These components are an execution and management model, Java™ EE and Java SE execution components, the execution unit (XU), and a persistence layer with decision services driving rule execution.

Rule Execution Server components
Rule Execution Server is an environment for executing rules. It provides management, performance, security, and logging capabilities.
Execution and management stacks
The execution, management, and monitoring stacks are similar for Java SE and Java EE but the packaging and lookup mechanisms differ.
Rule Execution Server model
The management and monitoring model acts as an application-specific interface to manage business logic, including remote updating and browsing. You can access that management and monitoring model by using various tools.
Execution unit (XU)
The execution unit (XU) is a resource adapter for Java EE Connector Architecture (JCA) 1.5. The XU handles the low-level aspects of ruleset execution and collaborates with the server to manage resources.
Rule Execution Server persistence layer
You can store RuleApps as archives in a file persistence or database persistence system. The persistence layer provides a solution for file persistence (file system) or for database persistence (JDBC or data source).
Transparent decision services
You can access Rule Execution Server through a web service.
Decision Warehouse
Decision Warehouse is a tool of the Rule Execution Server console for monitoring ruleset execution. It stores execution traces in a database.

Parent topic: Managing rule execution in Rule Execution Server