Creating the Decision Server database

Unless you are using Derby Embedded, database creation is a mandatory first step so that you can connect the data source when you deploy the Decision Server archives.

Create an empty database or obtain the database credentials if the database already exists. Then, you can create the database schema from the Rule Execution Server console after you deploy the management archive.

Alternatively, you can create the database schema immediately by running SQL scripts. The scripts that create the database schema and populate the tables are available in <InstallDir>/executionserver/databases:
  • repository_<DatabaseName>.sql: Support for the core RuleApp and ruleset persistence.
  • xomrepository_<DatabaseName>.sql: Support for the XOM libraries and resources persistence.
  • trace_<DatabaseName>.sql: Support for the Decision Warehouse persistence.
  • decisionrunner_<DatabaseName>.sql: Support for the Decision Runner persistence. These tables are required to run simulations in the Decision Center Business console.
The following table shows the conditions that apply.
Condition on... Description
db2 or db2_os390 schema The Decision Warehouse table space requires a buffer pool that has a page size of 32K. BP32K is expected in SYSCAT.BUFFERPOOLS. Use the following command to query SYSCAT.BUFFERPOOLS for the existing buffer pool:
Select * from SYSCAT.BUFFERPOOLS
Otherwise, use the following command to create a buffer pool named BP32K: 
CREATE BUFFERPOOL BP32K SIZE 2000 PAGESIZE 32K
You must update the trace_db2.sql script and select the custom option in the Installation Settings wizard to run it. Modify the following line in the script to specify storage for tablespace: 
CREATE TABLESPACE RESDWTS PAGESIZE 32K BUFFERPOOL BP32K;
Here is an example of the tablespace specification in the script:
CREATE  TABLESPACE RESDWTS PAGESIZE 32K MANAGED BY Database USING [ FILE 'C:\DB2\Container.file' 640 ] BUFFERPOOL BP32K;
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 must 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 Decision Server database is case sensitive.
To access the database, you must obtain the following credentials and privileges:
  • Database user name and password
  • Complete privileges on the tables, and a view of the schema (create, insert, delete)
  • Create index privileges
  • On Oracle, create trigger and create sequence privileges