Skip to content

Latest commit

 

History

History
57 lines (38 loc) · 4.35 KB

tut_cloud_rddebug_intro.md

File metadata and controls

57 lines (38 loc) · 4.35 KB
Raw

Tutorial scenario and prerequisites

In this tutorial, you work as a developer for a fictitious loan company. You are currently working on a decision service that validates loan requests. Called the Loan Validation Service, the decision service applies several criteria to determine the eligibility of potential borrowers, and contractual constraints for approved loans.

Scenario

A business user is reviewing the results of the decision service. The user contacts you to tell you that the decision service rejects low-risk loans that actually qualify for approval. You must debug the decision service to determine why it rejects the loans.

In Rule Designer, you tag rule artifacts with breakpoints that stop the running of the decision service at key points. You can then examine the behavior of the rules in a step-by-step debugging process. You determine where the errors take place, and track them to specific rules. Then, you modify the rules to fix the errors.

Prerequisites

You need the following component, projects and information:

  • Knowledge of business rule programming principles, Java™, and the Eclipse environment

  • Rule Designer: Download this component from the Operational Decision Manager on Cloud portal, and install it as directed.

  • The following project files in the Tutorial: Debugging a decision service in Rule Designer GitHub repository:

    • answer: Contains the completed version of the decision service. You can run it to see the expected results.
    • start: Contains the faulty version of the decision service. You look for errors in it during the debugging process.

In the GitHub repository, click the Clone or download button to download the contents of the repository to a directory on your computer. Expand the downloaded file in the directory. In the tutorial, the directory is referred to as InstallDir.

Best practices

This tutorial includes the following best practices for debugging decision services:

  • Carefully read the error messages. They tell you where to look for errors.
  • Try automatic exception handling when an exception occurs in a rule condition.
  • Check the stack trace to get the names of ruleflows and rule tasks.
  • Switch to the debug mode to get more precise error information.
  • Use the rule search to find artifacts, and the Java search to find Java XOMs.
  • Use queries to find rules by their content.
  • Check the values in the Variables view at each breakpoint during debugging.
  • Check the Agenda view to see which rules are going to be run.

More information

Use these links to find additional information:

Next ""

"" Back to table of contents

© Copyright IBM Corporation 2018