Memory persistence in Java SE
Memory persistence empowers an execution unit (XU) to load a RuleApp into an in-memory repository. It simplifies the RuleApp deployment because it frees you from having to set up a Rule Execution Server database or file persistence system to store RuleApps and rulesets.
Restriction:
The memory persistence can be used for XU only.
The memory persistence is not supported in the following features:
- Cascading ruleset execution
- XU as a resource adapter
- POJO sessions
- Decision Warehouse traces
- Monitoring feature in the Rule Execution Server console (XU execution statistics)
It is convenient for any Java™ SE integration use case, where RuleApps can be statically packaged within the Java application. This solution is useful for embedding rule execution capability into an Apache Hadoop or Apache Spark application.
You can use RuleApps in the memory persistence in two ways:
- Explicitly load a RuleApp archive into the memory persistence that is accessed by the XU.
- Implicitly load a RuleApp archive by using automatic strategies.