Task 5: Testing in the execution server

You find the RuleApp from the decision service in the execution server, and look at its contents.

1. Return to the cloud portal, and launch the Rule Execution Server (Development) console in the development environment.
2. Click the Explorer tab in the console.
3. In the Navigator, expand RuleApps, and then /Miniloan/1.0.
   Your RuleApp contains the ruleset Miniloan_ServiceRuleset:

   

   The RuleApp might contain more than one ruleset. You can find yours by looking at the creation dates.

4. Click Miniloan_ServiceRuleset to open the ruleset in the Ruleset View.
   The Ruleset View shows information about the ruleset, including its name, version number, and creation date, and provides commands for viewing performance information and adding elements such as properties:

   

You test the ruleset to determine whether it executes correctly. You use the REST API to run the test on manually entered data.

1. Click Retrieve HTDS Description File in the Ruleset View.
   The file retrieval page opens.
2. Select REST as the service protocol type, and OpenAPI-JSON as the format.
3. Click Test.
   The Hosted Transparent Decision Service (HTDS) opens.
4. Enter the following data as the run request:

   {
       "loan": {
           "amount": 500000,
           "duration": 240,
           "yearlyInterestRate": 0.05
        },
         "__DecisionID__": "Test",
         "borrower": {
           "name": "Joe",
           "creditScore": 600,
           "yearlyIncome": 80000
         }
   }

   Your run request should look as follows:

   
5. Click Execute Request.
   You get the following server response:

   

   The rule application produces the expected results. The loan is rejected, and a message explains that the dept-to-income ratio is too big.

6. Close the REST Service window.

Satisfied that the rules work as expected, you return to the Business console to deploy the rules to the test environment. The integrator runs integration tests on the rules in the test environment. These tests determine the stability and reliability of the rules under load before they are promoted to the production environment for use with client applications.

1. Return to the Business console, and open your branch in the Miniloan Service decision service.
2. Open the Deployments tab. In Configurations, click Test.
3. Open the Targets tab.
   The Test configuration deploys the rules in the decision service to Rule Execution Server in the test environment.
4. Return to the Deployments tab, hover over Test, and click the Deploy button next to the name of the deployment configuration.
   The deployment dialog opens. It shows the Server Test Environment as the target of the deployment.
5. Click Deploy, and click OK in the deployment status box.
   The list of reports opens in the Deployment tab. The new report shows that the rules have been deployed successfully:

   
6. Return to the cloud portal, and launch the Rule Execution Server (Test) console in the test environment.
7. Open the Explorer tab in the console.
8. In the Navigator, expand RuleApps, and then /Miniloan/1.0.
   Your RuleApp contains the ruleset Miniloan_ServiceRuleset:

   
9. Click Miniloan_ServiceRuleset to open the ruleset in the Ruleset View.
   The Ruleset View shows information about the ruleset, including its name, version number, and creation date, and provides commands for viewing performance information and adding elements such as properties:

   

   The integrator can now do nonfunctional and integration testing on the rules before they are deployed to the production environment.

   Tip: The test shown in step 2 works in Rule Execution Server in the test environment.

When the integrator finishes testing the rules from the decision service, the rules can be deployed to the production environment. Client applications then call the rules from this environment to process data.