| Samples > Rule Scenario Manager Demonstration > How to Test Rules in Rule Scenario Manager using XML Binding |
How to Test Rules in Rule Scenario Manager using XML Binding |
PREVIOUS NEXT |
This sample shows how to test rules in Rule Scenario Manager using XML data binding.
Scenarios can be grouped together into scenario suites. A scenario suite is a list of scenarios with a KPI that is calculated over the scenario results. See Scenario Suites for a more detailed description.
A simulation is a list of scenario suites together with a KPI, which provides global feedback on the executed scenarios. See Simulations for a more detailed description.
Scenario, scenario suite and simulation executions produce reports in different formats that you can view and store.
Note that most Rule Scenario Manager artifacts can be generated using a wizard. For more details, see Defining Rule Scenario Manager Artifacts.
Key features include:
To install the sample:
scenariomanager > basics-xmlbinding.
deploy.ruleapp command to deploy to the Rule Execution Server the loanvalidationruleapp RuleApp used in this sample.
Deploy succeeded.
build command to compile the source code.
This sample can only be opened and run in the Samples Console.
When executing the following scenario suite, you can view the results in Excel and HTML format.
To run a scenario suite:
run.scenariosuite target.
<InstallDir>/scenariomanager/samples/basics-xmlbinding/data/scenario/reports/excel.
BalXMLBindingInputReport1.xls file. This report file contains all data related to the execution:
run.report target.
<InstallDir>/scenariomanager/samples/basics-xmlbinding/data/scenario/reports/junit.
index.html file in your browser.
MyScenarioSuiteJUnit link in the left pane. The results of the execution are displayed in the right pane:
This sample helps you to generate the input data files from your XML files.
To generate the data input files:
run.dynamicinputparameters target.
<InstallDir>/scenariomanager/samples/basics-xmlbinding/data. You will see that an XML input data file dynio.xml has been generated.
Note that if you have installed Rule Studio, you can import this sample as a Java project.
To import the sample as a Java project:
<InstallDir>/scenariomanager/samples/basics-xmlbinding.
build.xml file to run the tests.
This sample is located in the directory: <InstallDir>/scenariomanager/samples/basics-xmlbinding.
Highlights of this sample are as follows.
As the rules are executed against a dynamic XOM, there is no need to deploy the SSP WAR file.
Environment configuration data, which can be applied to scenarios, scenario suites, and simulations, are contained in XML files. See Databinding for an explanation of how scenarios are controlled by their configuration.
You use this XML data configuration to define the following:
In this sample, the configuration is specified by the loanValidationConfigurationXML.xml file or the loanValidationConfigurationExcel.xml file. These files specify the properties required to execute the scenarios, such as the executor class and the input and output databinding classes.
Note that all requests for executions are sent to a remote Scenario Service Provider through the IlrHTTPExecutorImpl executor. This class allows you to execute rulesets remotely using the HTTP protocol.
The configuration also defines the method by which the input data is read. To read XML data, the configuration specifies IlrXMLInOutParametersImpl as the input binding class. To read Excel data, the configuration specifies IlrExcelInOutParametersImpl as the input binding class.
The Rule Scenario Manager testing artifacts, scenarios, suites and simulations, are defined in XML files.
You use this XML file to define scenarios using the following data:
Input data is the source data on which a ruleset (defined by the ruleset path) is executed.
After the ruleset is executed, an execution response is generated. The response includes such information as the time taken to complete the ruleset execution, the rules fired, the tasks executed, the number of rules fired, the number of tasks executed, and so on. You can use filters to determine how much information you retrieve from the ruleset execution. See Filters for further information.
A scenario report represents the results of a scenario execution. It contains the name and description of the scenario, the tests that were performed over the ruleset execution results and the test results. Output data is the data returned by the rule engine on the execution of the ruleset; they are the results of firing the rules.
You use this XML file to define scenario suites using the following data:
To generate the input files from the XML files:
BalXMLBindingSuiteXML.xml file contains the list of scenarios to execute. The scenario files use XML and Excel input data. BAL XML Scenario 1 and BAL XML Scenario 2 use XML input data while BAL XML Scenario 3 uses Excel input data. The following files are used in this sample:
myPackage/MyScenarioSuiteJUnit.java
BalXMLBindingConfigurationXML.xml
BalXMLBindingSuiteXML.xml
To rebuild the sample:
build target to compile the code.
run target.
run.report target.
deploy.ruleapp target.
| Copyright © 1987-2008 ILOG S.A. All rights reserved. Legal terms. Documentation homepage. | PREVIOUS NEXT |