Guide‎ > ‎

Business Logic Console

You can use the Business Logic Console to monitor the performance and operation of your business logic.

The console is appropriate for a multi-user environment.  When you are doing unit testing, use the facilities described in logging and debugging.


The Business Logic Console depends on JPA services, so requires a J2EE container for operation.  It operates as a web application, from this url, which connects the default port.  Or, you can run this url, which enables you to specify your address and port number.

Performance Summary

To view the Summary Pane, click Performance on the left menu, and then select the Summary tab.  This shows the execution count / time for each rule.

Performance By Rule

Click the By Rule tab to see a Bar Chart of executions, or total / average time for rule execution.  You can use this to identify rules that require an abnormal amount of time to execute, or are never executed.

Performance by Object

You can use the Object tab to get a more granular of logic execution.  You might use this to identify high volume objects, and then focus on specific rule performance using the previous display.


Use the Transactions display for a log of transaction execution.  To view this display, you must first Start this service using the buttons above.  You can then select a transaction from the rotating list shown with time stamps to see all the rules that fired within that transaction.  Notice the indentation level illustrates Forward Chain nesting.


This page enables you to find rows that do not meet the logic declarations.  In particular, this will identify:
  • Rows that do not meet constraints

  • Row for which Sum/Count values are not accurate

  • Action and Formula rules are not considered
This can happen when rules are changes (and the data might not match the new rules), or when data is bulk-loaded from an external source.  You can use SQL tools to repair the data, and then re-verify using the Business Logic Console.