Changing persistence parameters

You can change the persistence type for the ruleset repository. If you have set up Java™ XOM management, you can also change the persistence properties for the XOM repository. You must set the persistence t to the same type in both the console and the execution unit (XU) archive.

Changing the ruleset persistence type in the console
You can change the persistence type at the console level by modifying the values of context parameters in the deployment descriptor.
Changing the ruleset persistence type in the XU by using the deployment descriptor file
You can change the persistence type to a file system, a database, or memory for a rule set in the ra.xml deployment descriptor file.
Changing the ruleset persistence type in the XU by using APIs
You can change the persistence type to a file system, a database, or memory for a rule set by using APIs.
Changing the Java XOM persistence type
If you set Java XOM management for a ruleset, you can specify the persistence properties for the XOM repository.
Changing the persistence type by using an Ant task
You can change the persistence type by using the ressetup.xml Ant script.
Adding database user access to the persistence type
You can add user access to the ruleset repository if the persistence type is set to database mode.
Setting concurrent access rights
For file and database persistence types, you can specify that multiple execution units (XU) can concurrently access a ruleset in the persistence layer. For the memory persistence type, the concurrent access is always enabled and you cannot disable it.

Parent topic: Changing the default behavior of the execution stack

Related concepts:

Rule Execution Server persistence layer