This document describes the following configuration tasks in detail:
Creating record stores in CAS for product data and for the dimension values used in hierarchical and range dimensions.
Loading product data from external systems into product data record store(s) in CAS.
Loading configuration for hierarchical dimensions into dimension value record store(s) in CAS.
Configuring dimensions, dimension values, and Endeca record properties.
Configuring hierarchical dimensions by specifying parent/child relationships among dimension values. These hierarchies will enable visitors to your web pages to navigate to the content for which they are looking. Logical hierarchies do not apply to dimensions that you generate automatically, as explained in Introduction: flat dimensions and hierarchical dimensions.
Configuring how visitors can query the content on your site for specific product information.
Creating indexed records by submitting your product data and configuration to dgidx, the indexing process of MDEX. The product data and configuration are submitted to dgidx when you run a process known as a record store merger.
Note
When dgidx indexes Endeca records, it converts them to an internal format that makes it possible for them to be handled by dgraph, the runtime process of the MDEX engine. Because this format is entirely internal, it can be taken for granted and is not documented.
This document describes the following configuration tasks only briefly and refers you to other guides for more information:
This document does not describe the following types of tasks, which ordinarily must be performed to implement a Guided Search application:
Configuring the Assembler, which accesses values from a variety of sources, including databases, Digital Asset Management systems, social media feeds, and the MDEX engine. The Assembler also creates application components known as cartridges, which your application renders visually as UI controls or other components of the pages on your web site. For information about the Assembler, refer to the Oracle Commerce Guided Search Assembler Application Developer's Guide.
User Interface design, which concerns the arrangement and appearance of content on your web pages. You can write your front end application using any languages, development tools, or other resources. The Discover Electronics reference application provided with Guided Search is a sample front end application, written in JAVA. For information about the tools that Guided Search provides to help you create your user interface, refer to the Oracle Commerce Guided Search Assembler Application Developers' Guide and the Oracle Commerce Workbench User's Guide (for information about the Experience Manager).
Administrative tasks, which are performed both before an application goes into production and while it is in production. Creating user accounts and user groups, defining credentials, setting up sites, assigning privileges to users and groups, running updates, and scheduling reports are typical administrative tasks. For information about the administrative tasks that you must perform to support a Guided Search application, refer to the Oracle Commerce Guided Search Administrator's Guide.