Testing ruleset execution

You can test the execution of a particular ruleset through a testing interface.

Before you begin

To test rulesets with a managed Java™ XOM, you prepare for the test in one of the following ways:
  • Construct the Java input parameters by using the options provided in the interface.
  • Temporarily set the ruleset.managedxom.uris ruleset property to the location of the Java XOM .jar files.
    Tip:

    When you add this property to a ruleset, all execution requests use this same property value. In a production environment, this is unlikely to be the intended behavior.

About this task

Rule Execution Server features a web-based testing interface in which you specify an input request in the form of a JSON or XML document, and call a deployed ruleset. This interface is part of the hosted transparent decision service (HTDS) web application. You navigate to that interface from a ruleset in the Rule Execution Server console.

Restriction:
  1. The web testing interface is not a programmatic interface and is not designed for automated execution.
  2. You must have at least one instance of the HTDS web application running and correctly configured for this feature to work properly.

Procedure

  1. In the navigator tree, browse through the RuleApps tree, then click the relevant ruleset.
  2. In the ruleset view, click Test ruleset.

    The testing interface generates a sample request that can serve as a base and be completed or modified before being sent.

  3. Click Execute Request.

Results

If the execution is successful, the testing interface displays the server response in a box at the bottom of the page. It contains the JSON or XML response document.

If the execution fails, a pop-up message reports the error and its cause.