Step 1: Selecting and applying the persistence type

You can change the default datasource RuleApp and Java XOM persistence settings by running an Ant script that generates a new Rule Execution Server management archive.

Typically you do this if you are in development mode. This step does not apply to beginners using the embedded Derby database.

To change the persistence settings, the distribution provides an Ant script in the <ODM_InstallDir>/executionserver/bin/ressetup.xml file. Use it to create a new instance of the Rule Execution Server management archive and, in the case of a Java EE application server, the Execution Unit (XU).

Note:

If you use file-based persistence on Solaris, your file system must support all characters used in directory and file names that are present in the ruleset path (RuleApp name and ruleset name). Set the LANG system property with the encoding that is compatible with your package and rule names, for example en_US.UTF-8.
If you select the file persistence type for RuleApps, you cannot use Decision Warehouse.
MySQL persistence: If you choose to use MySQL as a persistence back end, add or set the following properties in the MySQL configuration file my.ini (on Windows) or my.cnf (on UNIX operating systems):
```
sql-mode=STRICT_ALL_TABLES
max_allowed_packet=1073741824
```
For more information about these settings, see the MySQL 5.0 reference manual: 5.1.6. Server SQL Modes and 5.1.3 Server System Variables.