Task 6: Monitoring

You monitor a running ruleset by using the Rule Execution Server console. You use Decision Warehouse to audit and view stored decision traces.

About this task

As an IT professional responsible for computer applications at your company, you must ensure that your rule-enabled applications are running correctly. In addition to providing an environment for managing the execution of your rules, Rule Execution Server can be used to monitor the execution of your rulesets.

Auditors can analyze the execution performance of rulesets, and troubleshoot any problems. To identify a problem when a transaction fails, auditors and analysts need to know the business policies that were applied, and the data that was used at execution time. Accessible from Rule Execution Server, Decision Warehouse stores ruleset execution traces that can be used for auditing purposes.

Deprecated feature:

Deprecation icon The Decision Warehouse is deprecated in V9.0.0. For more information, see Deprecated and removed features.

Step 1: Running Rule Execution Server diagnostics

You run the Rule Execution Server diagnostics to identify errors in the execution environment.

Procedure

  1. Open the Rule Execution Server console:
    • Windows:
      • Windows 10 or later: Start > All Programs > <ODM> > Rule Execution Server Console
      • Windows 11: Start > All appss > <ODM> > Rule Execution Server Console
    • On all platforms, enter the following URL with the correct port number in a web browser: http://localhost:<PORT>/res/
  2. Sign in to the Rule Execution Server console by using odmAdmin as the user name and password.
  3. Click the Diagnostics tab, and then click Rerun.
    A green check mark indicates a successful test of an aspect of the execution environment.
  4. Click Expand All to show the details of each test.
    The diagnostics test various aspects of the execution environment. Review the diagnostics, and then review the statistics on deployed RuleApps.
    Note: The local XU connectivity and two rule session execution entries are grayed out because the sample server uses the WebSphere® Liberty application server in J2SE mode. In J2SE mode, the eXecution Units (XUs) are embedded in the client applications, and the Rule Execution Server console does not have XUs.

Step 2: Viewing statistics on deployed RuleApps

When the execution environment is functioning correctly but performance problems are being reported, you can consult statistics from the Rule Execution Server console.

Procedure

  1. In the Rule Execution Server console, click the Explorer tab.
  2. In the navigator tree, expand RuleApps and select the ruleset my_deployment/1.0/my_operation/1.0.
  3. Click the Statistics tab to see the ruleset execution statistics.
  4. Open the Execution Units tab and click xuHTDS to see metrics that include the execution count, time and dates.

    You can see detailed information by expanding the execution unit section.

Step 3: Searching for past transactions in Decision Warehouse

You search for past transactions and decision traces in Decision Warehouse to find the decision that caused the failed transaction. There are traces of the decision history because you added the monitoring.enabled ruleset property.

Procedure

  1. In the Rule Execution Server console, click the Decision Warehouse tab.
  2. In the Search Decisions section, leave the fields blank, and click Search.

    Decision Warehouse displays the decisions for the transactions that you ran in the Miniloan application, including the date and the processing time.

Step 4: Viewing the run rules

You can use Decision Warehouse to determine why the application rejects a loan. You check the execution details for a decision and view the rules that were run.

Procedure

  1. In the table that lists the decisions that are stored in the Decision Warehouse, click the Decision ID for the decision in which one rule was run.
  2. Close the decision trace window, and sign out of Rule Execution Server.

What to do next

You monitored the performance of rulesets and traced transactions. In the next task, you publish the rule project to Decision Center to make the rules accessible to business users in a shared web-based environment.