You can configure and customize Decision Warehouse to go
beyond the built-in capabilities.
About this task
You can use steps 3, 4, and 5 in the following workflow to configure and customize
Decision Warehouse.
There is a dependency between step 3 and step 4. You cannot select a custom data source from a
calling application unless you added new data sources. These two steps are configurations of
Decision Warehouse, whereas step 5 is a customization of what is stored within the execution
trace.
Procedure
- Install and create database resources.
- Enable ruleset execution monitoring.
- Add new data sources to Decision Warehouse in the Rule Execution Server console.
- Select a specific data source to store the results of ruleset
execution.
You can do so in the Rule Execution Server console
and in a client application.
- To optimize what is stored in Decision Warehouse, add the monitoring.filters and monitoring.inout.filters ruleset
properties to the ruleset through the ruleset view in
the Rule Execution Server console.
Restriction: You cannot use the monitoring.inout.filters property
to filter elements in the BOM representation of ruleset parameters.
- Execute the ruleset.
- View the stored results in Decision Warehouse.