Before you start

This tutorial shows you how to debug a loan validation application that is running on a remote server.

If you intend to follow this tutorial on an application server other than the sample server installed with Decision Server, you must install Rule Execution Server and the Scenario Service Provider (SSP) component on this server before you start. For more information, see the installation information for Rule Execution Server.

A loan company implements a loan validation policy that evolves continuously and provides a loan validation application for its agents.

The application has the following purpose:

Validate input data from a web application.
Calculate its customer eligibility given the personal profile, the score, and the requested loan amount.
Evaluate specific criteria or scores to accept or reject the loan.
Compute an insurance rate from a function of the computed score if the loan is accepted.

The application ruleflow is as follows:

flowtask main
{
  body   {
    initResult;
    dataValidation;
    if (?context.?report.isValidData())
    {
      computation;
      eligibility;
      if (?context.?report.isApproved())
      {
        insurance;
      }
    }
  }
};

Next Start this tutorial:Task 1: Deploying the loan validation application

In this tutorial, you deploy the loan validation web application. Then, from Rule Designer, you import the corresponding rule project and create a RuleApp project, so that you can deploy the loan validation RuleApp to Rule Execution Server. Then, you execute the application ruleset and analyze the results. Because you find an error in the execution, you enable debugging on the ruleset and on the application server. Finally, you embed and deploy the loan validation application with a Scenario Service Provider (SSP) client.

This tutorial takes about two hours to complete.

Directory structure

In this tutorial, <TutorialsDir> refers to the tutorial installation directory, by default, <InstallDir>/executionserver/tutorials.

The <TutorialsDir>/resdebugging directory has the following structure:

The shared directory is for source files that are shared by several tutorials.
The task1/ directory contains the build.xml Ant build file for each supported server and a number of descriptor files.
The task4/ directory contains the rule project and its XOM project.
The work directory contains the readme file. It is your working directory, where you copy the contents of a start directory when necessary and save your work.

The following table describes the structure of the <TutorialsDir>/resdebugging/shared directory.

Table 1. Structure of the resdebugging tutorial
Directory or file	Description
data/	This directory contains the LoanValidationRs.jar RuleApp archive that is used by the tutorial.
/WebContent	This directory contains the following JavaServer Pages and subdirectories. borrower.jsp error.jsp executerules.jsp executerules_tomcat.jsps footer.jsp header.jsp index.jsp loan.jsp processborrower.jsp processloan.jsp css/* images/* WEB-INF/*
/src	/web/*

What you need to know

You must at least be familiar with Java™ EE technologies: Java EE packaging and deployment, JSP.

Next Start this tutorial: Task 1: Deploying the loan validation application

Before you start

Directory structure

What you need to know

Lessons in this tutorial