ILOG JRules User Guide > Running and Debugging > Tasks > Debugging > Stepping Through the Execution

In the Debug Perspective, you can step into the code to debug your rules.

To step into your IRL code:

  1. Click Run > Debug. The Debug dialog box opens.
  2. Select your configuration in the Configurations pane.
  3. Make sure you select the Stop at first rule statement check box.
  4. Click Debug. The Debug Perspective opens, and execution stops at the first rule statement to be executed.
  5. From this point, several stepping options are available to you:
    1. To invoke the next expression and suspend execution at the next non-filtered executable line, click Run > Step with Filters or click the Step with Filters button.
    2. To invoke the next Java or rule statement and suspend execution at the next Java or rule line, click Run > Step Into or click the Step Into button.
    3. To invoke the next Java or rule statement and suspend execution at the next rule line in the next rule, function, or rule task, click Run > Step Over or click the Step Over button.
    4. To invoke the next Java or rule statement and suspend execution at the first rule statement of the next rule, function, or rule task, select Run > Step Return or click the Step Return button.

Related Concepts

Ruleset Debugging
Rule Engine

Related Tasks

Starting a Debugging Session
Setting Breakpoints in Rules
Setting Breakpoints in the Working Memory
Setting Breakpoints in the BOM
Inspecting the Working Memory
Inspecting the Agenda
Viewing and Evaluating Expressions
Viewing and Editing Variable Values
Viewing Breakpoints

Related Samples and Tutorials

Tutorial: Debugging a Ruleset
Tutorial: Debugging a Remote Rule Execution Server Application