Debugging

In Rule Designer, start a debugging session and use the debug tools to test and evaluate your business rules.

Ruleset debugging tools
Use the Rule Designer debug tools to make sure that your rule application projects run as expected.
Starting a debugging session
You start a debugging session to test your rules and evaluate the runtime performance of a ruleset.
Setting breakpoints in rules
You can set breakpoints on rule expressions to perform a step-through analysis of the rules.
Setting breakpoints in the working memory
You can set breakpoints on objects in working memory if you want execution to stop when the objects are retracted or updated.
Setting breakpoints in the BOM
You can set breakpoints on business object model (BOM) classes to stop execution when an object is added, retracted, or updated.
Stepping through the rule execution code
You can use the Debug Perspective to step into the code to debug a rule, except in sequential mode.
Inspecting the working memory
You can inspect the objects in working memory when the execution mode is RetePlus.
Inspecting the agenda
You can inspect the rules placed in the agenda when you debug a rule project or a Java™ project for rules.
Viewing and evaluating expressions
You can inspect expressions in the context of a stack frame when the Virtual Machine suspends a thread because it hits a breakpoint or it is stepping through code.
Viewing variable values
You can view the variables in a stack frame.
Viewing breakpoints
You can view the breakpoints that you have inserted.

Parent topic: Running and debugging