Endeca MDEX Engine Basic Development Guide Version • March Guide and are familiar with the Endeca terminology and basic concepts. Endeca focused on this e-commerce market first, and developed the Guide and influence customers at each step of their experience to. Endeca MDEX Engine: Basic Development Guide – Oracle Read more about dimension, record, endeca, mdex, query and engine.

Author: Gromi Mazugal
Country: Ghana
Language: English (Spanish)
Genre: Photos
Published (Last): 20 March 2012
Pages: 403
PDF File Size: 15.53 Mb
ePub File Size: 19.9 Mb
ISBN: 676-5-13708-807-7
Downloads: 3783
Price: Free* [*Free Regsitration Required]
Uploader: Vok

For stratumInt, a positive integer will boost the dimension value while a negative integer will bury it. NET return the properties as a PropertyMap object of the aggregated record. Once this loop is initiated, bwsic DimGroup object is created.

About phrase search Phrase search allows users to enter queries for text matching of an ordered sequence of one or more specific words. In some cases, the user may want location and order to be considered when matching searches. Using this flag improves performance of text search with phrases. Most applications have a navigation page and a record page, but each application has its own requirements.

A common user interface mechanism for overcoming this is to create pages of results, where each page displays a subset of the entire result set.

wcs: Endeca: A Simple developer OverView

A snippet for each matching record displays on a record list page: Statistics on aggregated records are returned as a property on each dimension value. The following are examples of snippeting in queries: Conventions used in this guide This guide uses the following typographical conventions: Dimension Value Boost and Bury Refer to the comments in the individual module files for more detailed information.

In this instance, the JavaScript returned with the page will not be useful, because it references a browser request that has since been modified. The following example shows one EQL expression for the module: This transformation process does not change the content of your source data, only its representation within your Ddvelopment implementation.


Functions as a repository for variables that do not change across requests.

Endeca MDEX Engine: Basic Development Guide – Oracle …

Ancestors property For example, if a Wineries dimension contained four levels of hierarchy Country, State, Region, Winery and the current query was at the region level Sonoma Valleythe ancestor list would consist of the dimension value United States first and the dimension value California second: The worst-case scenario for run-time performance is having a data set with a large number of dimensions, each dimension containing a large number of refinement dimension values, and setting the ENEQuery.

The application modules use Presentation API method calls to retrieve and manipulate the query results. Displaying descriptors Displaying descriptors is the ability to display a summary of the navigation refinements that have been made within the current navigation query.

This is because the properties and dimensions do not need to be explicitly endecz as valid for range filters in the same way developmeht they need to be explicitly identified as valid for record search.

Examples of Query Matching Interaction To configure disabled refinements, you do not need to change the Endeca project configuration XML files used with Forge, Workbench, and Developer Studio. Working with Endeca Records NavNumERecs property The default number of returned records is You should remove the displayKey parameter from a production deployment as the record names develppment never change. The use of JavaScript is completely optional. That is, if any one particular server goes down, a replica of an MDEX Engine provides redundancy by allowing other servers in the implementation to continue to reply to queries.

Properties generally contain more detail about a record than the higher-level dimension values used for navigation.


The main purpose of dimension values is to enable navigation through the records. There is no configuration associated with the properties and they cannot be disabled.

NET to specify query parameters. You first create a refinement configuration for each dimension value by using the calls of the RefinementConfig class. The other parameter required in most cases to render navigation refinements is the Ne Exposed Refinements parameter.

XMetaL WebHelp

This is called positional indexing. In this case, the refinements from the other siblings will not be exposed. Indicates the presence of incompatible modules in the Endeca application discovered while attempting to process a query. After the indices are stored, the MDEX Engine receives client requests via the application tier, queries the indices, and then returns the results.

Endeca MDEX Engine: Basic Development Guide – Oracle –

Renders a list of records that have been aggregated based on a rollup key. Regardless of how you choose to build them, the application modules should perform the following functions: You can determine whether there are more refinements by checking the DGraph. Depending on the environment you are working in, the Presentation API can take several different forms: Also, most phrase searches performed tend to contain at least one information-rich, low-frequency word, allowing results to be returned rapidly that is, in less than a second.

The stratified dimension values are delimited by semi-colons ; and each stratified dimension value is in the format: Range filters can be applied to either properties or dimensions of the following types: