Creating a schema for the Rule Execution Server database

After you deploy the Rule Execution Server management archive, the schema for the Rule Execution Server database must be created.

If you did not create the database schema using SQL scripts when you created the database, the Installation Settings Wizard guides you through the creation of the database schema the first time you sign in to the Rule Execution Server console, on Windows or other distributed platforms.

The Installation Settings wizard creates all the required tables for RuleApp persistence and Decision Warehouse trace. Then, optionally, the Installation Settings wizard creates the tables for the persistence of the managed Java™ XOMs.

If you are using file persistence or have an existing database schema, the Installation Settings wizard does not open when you sign in to the Rule Execution Server console. If you want to modify the database schema after you create the database tables, you must run the SQL scripts manually.

In the Installation Settings wizard, you can choose the option to remove tables from the database. Ensure that you have a backup of your database resources.

For more information on how to grant sufficient user access to the Oracle tables necessary for XA transaction recovery, please consult the RedHat Customer Portal and the Oracle documentation for Oracle 12 (or Oracle 11).

The following conditions apply when you create the database schema:
Condition on... Description
db2 or db2_os390 schema If you select a db2 or db2_os390 schema, an extra field opens so that you can enter the name of the buffer pool, which is used to create the Decision Warehouse tablespace. This buffer pool must have a page size of 32K. Check the DB2® documentation for information about how to create a 32K buffer pool.
Automatic storage The scripts for creating the Decision Warehouse database on DB2 are written for databases that use automatic storage. If you have not configured your DB2 database to use automatic storage, you cannot use the Rule Execution Server console to create the Rule Execution Server tables. In this case, use the SQL script to generate the database schema.
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 reference manual: Server SQL Modes and Server System Variables.
SQL collation The Rule Execution Server database is case sensitive.

Run the Installation Settings wizard as follows:

  1. Open the Rule Execution Server console, typically by typing res at the root URL on the host machine: http://localhost:<port>/res.
  2. Sign in with administrator rights (for example, on the sample server, resAdmin / resAdmin+0).
  3. Choose a database type to create a schema that contains the necessary tables and views and follow the Wizard.
  4. For the Decision Runner, run Diagnostics first, and in the Decision Runner section, follow the link to the Wizard to create the tables (link visible only if the tables do not already exist).