Loading Precedence Rules

This chapter describes how to load your precedence rules into the MDEX Engine.

About precedence rules
A precedence rule allows your application to suppress refinements for an Endeca attribute until some condition is met. This makes navigation through the data easier and is essential to avoid information overload problems.
Schema for precedence rules
Each precedence rule is represented as a single record in the MDEX Engine.
Format of the precedence rules input file
The input configuration file should contain five configuration properties and a corresponding set of value data.
Adding components to the precedence rules graph
You must add the UniversalDataReader, Reformat, and WebServiceClient components to the graph.
Configuring the precedence rules Reader
This task describes how to configure the UniversalDataReader component to read in the configuration file for creating precedence rules.
Configuring the Reformat component for precedence rules
A Reformat component is used to transform incoming configuration data into a precedenceRule record.
Configuring the precedence rules WebServiceClient component
The WebServiceClient component must be configured with the WSDL of the MDEX Engine's Configuration Web service.
Deleting precedence rules
The config-service:deletePrecedenceRules operation lets you remove an existing precedence rule from the MDEX Engine.