Rule Execution Server persistence layer

You can store RuleApps as archives in a file persistence, database persistence, or memory persistence system. The persistence layer provides a solution for file persistence (file system), database persistence (JDBC or data source), or memory persistence (memory).

You can set the persistence type to one of the following values:
  • file for a file persistence in Java™ SE
  • datasource for a database persistence in Jakarta EE
  • jdbc for a database persistence in Java SE
  • memory for a memory persistence in Java SE
For information about how to set or change the persistence type, see Changing persistence parameters.

File persistence and database persistence that use light embedded databases, such as H2, are easy to configure. Developers can easily write prototype projects and quick demonstrations.

When a new version of a ruleset is added to the management model, a notification of the update is sent through the Java Management Extension (JMX) or through the TCP/IP connection services to the execution unit (XU). The XU receives the new resource.

Important:
  • The ruleset persistence settings must be the same in the execution unit as in the Rule Execution Server console; however, this rule does not apply to the memory persistence. See Changing the ruleset persistence type in the console.
  • Use database persistence when you deploy to a Jakarta EE cluster environment. If you use file persistence, there is a risk of inconsistency. If, nevertheless, you choose to use file persistence with a clustered Rule Execution Server, you must make sure that all instances have access to a common network file system.