The Relevance Ranking Evaluator requires an MDEX Engine to produce its results.
It is not necessary to dedicate an MDEX Engine solely for use by the evaluator. The MDEX Engine that you use can be shared by another Web application or instance of your Website. Oracle recommends that the MDEX Engine be in a staging or QA environment, where the configuration is stable and does not compete for resources with production.
While you can use Relevance Ranking Evaluator with any MDEX Engine, there are certain configuration options that enhance the information and user experience. These configuration options are optional, and are not required to use the evaluator. For more information on these options, please refer to the MDEX Engine Developer's Guide.
whymatch: Relevance Ranking Evaluator can take advantage of the information returned by either the --whymatch (recommended) or --whymatchConcise command-line MDEX Engine options. If one of these options is enabled, Relevance Ranking Evaluator displays specific information about how each record was matched by the search terms that a business user entered. Use these options with care in a production environment, since they might degrade run-time performance.
wordinterp: Relevance Ranking Evaluator can take advantage of the information returned by the --wordinterp command-line MDEX Engine option. If this option is enabled, Relevance Ranking Evaluator displays word interpretations considered for the search query, including thesaurus and stemming expansions. Again, use this option with care in a production environment, since it might degrade run-time performance.
DGraph.BinRelevanceRank: When the MDEX Engine performs a relevance ranked search, it determines a relevance ranking score for each record, and uses that score internally to sort the results. This score, along with an indication of records that have the same the score, can be displayed by the Relevance Ranking Evaluator if the --stat-brel command-line MDEX Engine option is used. Like the other options, use this option with care in a production environment, since it might degrade run-time performance.
