Sample: Ruleset extraction

Description

This sample shows how to use ruleset extractors and how to filter rule project elements with extractors using queries and validators. The sample also shows how to generate and execute a ruleset archive.

You can define a custom extractor when:

• You want to have a single rule project and deploy rules (and other artefacts) at different locations.

  In this example, the data is hosted in each region and the aim is to deploy distinct Human Resources rules on the application server of each region, whilst keeping the rules in a single repository for ease of maintenance.

• You want to select only a subset of rules that are not required at runtime.

  For example, to ensure that no “test” rules or any rule matching a defined pattern is executed. In addition, you might want to discard expired rules or rules with an incorrect status. You can apply the filtering to any rule property and you are limited only by the Rule Designer API scope of the queries or by what is defined using the Rule Designer API inside validators.

The key features of this sample include:

• Development of an Eclipse plug-in using the exposed Rule Designer API.
• Use of existing extractors or creation of new ones.
• Ability to automate Rule Designer tasks through Ant tasks.
• Setting a query or a validator on an extractor.
• Checking if a query is defined in a rule project using Rule Designer API.
• Creating a validator by extending an Eclipse plug-in extension point.
• Checking if the validator is extending the Rule Designer validator extension point using Eclipse API.
• Creating a query using its text definition.
• Generating a ruleset archive using an extractor.
• Forcing the build of a rule project using the Eclipse API.
• Running the generated ruleset archive using basic Java™ code.