Integrating query extensions into Rule Designer

You use query extensions to create business-specific query predicates that process customized rule project items and properties. You integrate them into Rule Designer by creating a Rule Designer plug-in with a query model extension point.

Before you begin

Before you integrate query extensions into Rule Designer, make sure you have all the necessary files:

  • A BOM file

  • A vocabulary file

  • A BOM extender mapping file

  • One or more extender classes

About this task

You use query extensions to create business-specific query predicates that process customized rule project items and properties. To integrate them into Rule Designer, you create a Rule Designer plug-in with a query model extension point.

Procedure

To integrate query extensions into Rule Designer:

  1. Create a plug-in project that depends on the plug-in: ilog.rules.studio.model.query.
  2. In this plug-in, create an extension for ilog.rules.studio.model.query.queryModelExtension.
  3. Place your query extension files and classes in the src directory of the plug-in.
  4. In the extension details, set the following attributes:

    bom_url - the location of the BOM file

    voc_url - the base name of the vocabulary files (without the locale suffix)

    bom_extender_mapping_file - the location of the BOM extender mapping file

    For example, if you create three extension files named ext.bom, ext.voc, and ext.properties and place them at the root of the src directory in the plug-in project, the extension details are as follows:

    • bom_url: ext.bom

    • voc_url: ext.voc

    • bom_extender_mapping_file: ext.properties

  5. Save the plug-in project.
  6. Deploy the plug-in.

Results

Your query extensions are now available in your Rule Designer installation.