Overview of the Decision Center database schema

You can view and run reports against the Decision Center database schema. The database tables are generated automatically according to the rule model.

Note:

The database schema for the Decision Center repository is provided to help you understand how the repository operates. IBM® supports use of the schema to aid viewing or reporting from the repository, but documented changes to the schema in future releases of Operational Decision Manager might require corresponding changes to any SQL you use to view or report from the repository. IBM does not support use of SQL to modify directly the contents of the repository.

The database tables are generated automatically according to the rule model (see IlrModelInfo).

Some of the database columns are used to implement some features of the rule model.

For example, all rule model project elements contain a PROJECT column, which is a reference to the RULEPROJECT table. Aggregated elements are not project elements and therefore do not define that column. However, they all have a CONTAINER column that is a reference to the project element to which they are linked.

All enumerations from the rule model are stored in the database in the same way:

A column to store the values
A column to indicate whether or not the value is still in use (deprecated or not)

When a value is removed from an enumeration, it becomes deprecated. This means that existing instances that use this value can still refer to it, but new data cannot use it.

The scripts that create the tables are generated by Ant tasks.