Rule Builder > Debugging and Profiling > Testing the Execution of a Ruleset

There are several ways to use the Rule Builder when you test the execution of a ruleset. You can do one of the following:

Before you test the execution of a ruleset, make sure your XOM is properly set.

A rule engine is an instance of a class that derives from the class IlrContext (see the Java API Reference Manual and the Rule Engine User's Manual).

An engine has five states with regard to the Rule Builder, as shown in Table 16.1:

Table 16.1   Engine States
Engine stage 
Description 
Controlled  A call to IlrContext.delegateControl() has been performed in the application. 
Firing  The engine is firing rules, which means that a connected engine in an application called a firing rule method. 
Stopped  The engine has fired rules and has stopped in the action part of the currently executing rule, or at a breakpoint. 
Connected  The engine is executing code that does not fire rules. 
Disconnected  The engine is disconnected from the application but the Debugger and Profiler panels are accessible. 

To view information about the state of an engine, right-click the engine element in the Engine Explorer and choose Info in the shortcut menu.

See Also

Executing a Ruleset in the Rule Builder | Instantiating an Engine in a Separate Thread | Connecting a Remote Engine | Setting Up the Execution Object Model


Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. PREVIOUS   NEXT