Default use of Decision Warehouse

You can use the default Decision Warehouse to store the trace of a ruleset execution.

1. Complete the installation of Rule Execution Server and Decision Warehouse on your application server.

   Typically, you create database schemas for Rule Execution Server and Decision Warehouse by running the Installation Settings wizard from the Rule Execution Server console.

2. Enable ruleset execution monitoring by making sure that the following ruleset properties to true.
   • ruleset.bom.enabled
   • monitoring.enabled
   • ruleset.sequential.trace.enabled if the ruleset contains tasks that use the sequential or the Fastpath execution mode.

   Note:

   You can add these ruleset properties before or after deployment by working from Rule Designer or from the Rule Execution Server console. Rulesets that are built with the decision engine use only the monitoring.enabled property and do not need ruleset.bom.enabled and ruleset.sequential.trace.enabled. These properties are therefore ignored for such rulesets.

3. Execute the ruleset from testing and simulation, a client application, or a hosted transparent decision service.

   The execution trace data is written to the default Decision Warehouse database.

4. View the stored results in Decision Warehouse.
   Use the Decision ID to locate a specific transaction and view the executed rules. Decision identifiers (IDs) are generated automatically or manually.

   • By default, decision IDs are generated automatically. In this case, they are identical to the identifier of the execution unit (XU) connection.
   • You can also create decision IDs by using the rule session API.