The JAR files of the product distribution include a default
data source. You can customize how and where the trace data is stored.
About this task
Each application server has a default data source that
stores the execution traces of the rulesets that are enabled for Decision
Warehouse. As a developer, you can customize how and where the trace
data is stored.
Procedure
To store trace data in a customized data source:
-
Use the extension API to create a custom Data Access Object (DAO).
See the ilog.rules.res.persistence.trace package.
Your custom DAO implements the IlrTraceDAO interface.
Note: Make sure that the IlrTraceQuery instance that is returned by the IlrTraceDAO#createQuery()
method on your DAO returns an IlrCriteriaPart.IlrCriteriaPartStringPattern instance, not a
IlrCriteriaPart.IlrCriteriaPartString instance. This also handles the String value
that is passed to the IlrCriteriaPart.IlrCriteriaPartStringPattern#matches(java.lang.String) method
on this instance as a String value that contains * and
. characters to be treated as wildcard characters (the escape sequences being
\* and \.) at your data management level.
- Reference this object in the calling client.
- If you want to query the custom data source from the Decision
Warehouse tab of the Rule Execution Server console,
package your custom DAO in the Rule Execution Server console
web archive.