Customizing execution using the DVS API

You run tests in Rule Designer using the DVS API.

About this task

You use the DVS API to obtain, locally in Rule Designer, a detailed report with the same execution traces as Decision Warehouse. The tests connect to a local SSP service (Java™ SE implementation) to obtain a detailed trace of the ruleset execution. You can configure your client application to use custom formats, and include the SSP service and the Decision Warehouse trace components (see Sample: DVS archive testing using JUnit).

Procedure

To run a test using the DVS API:

Set the custom format on a formatDescriptor (an implementation of the IlrScenarioFormatDescriptor interface).
Set the formatDescriptor to an implementation of the IlrScenarioSuiteDescriptor interface.
Pass the scenarioSuiteDescriptor to an SSP service.
In Eclipse, you can use a local SSP service (IlrLocalSSPService) to perform a test without the full execution stack.
Obtain a scenarioTestResult from the IlrScenarioSuiteTestResult interface.
Get the executionId using the getExecutionId method and set it to a String.
Pass this executionId to an implementation of IlrDWTrace.
Send the DWTrace to System.out (the Console view).

Results

The returned trace is stored in local memory. This testing environment is subject to the memory limitations of the running Eclipse JVM, which determines the capacity to store this data.