Microsoft Dynamics AX 2012 R3 Retail Application Training -

Microsoft Dynamics AX 2012 R3 Retail Application-Installation and Configuration

Locus IT ServicesMicrosoft Dynamics AX 2012 R3 Retail Application-Installation and Configuration

Lesson 1: Search-Driven Sites

Search-Driven Sites

Lesson Objectives: Search-Driven Sites : The objective is to describe the concepts behind search in an Ecommerce setting.

Search-Driven Sites

The out-of-the-box starter storefront (shipped with the product) is fully functional and can serve as a starting point for creating a customized user experience based on specific needs.

  1. Term store: Holds the entire product hierarchy. SharePoint Server 2013 includes the Term Store Management tool, which you use to create and manage term sets. If you have the appropriate permissions, you can use the Term Store Management tool to perform the following tasks:
  • Create or delete a term set.
  • Add, change, or delete terms.
  • Arrange managed terms in a term set into a hierarchy.
  • Define synonyms.
  • Import terms.
  • Make enterprise keywords into managed terms by moving them into a term set.
  1. Catalog site collection: Holds the product catalogs that have been published from Microsoft Dynamics AX.
  2. Asset site collection: Stores images, videos, and other assets.
  3. Search index: Holds all content and metadata that has been crawled. To build the search index, you must first start a full crawl of content that is specified in one or more content sources.
  4. Publishing (rendering) site collection: Holds the online store (UI).

A content source is a set of options that you can use to specify what type of content is crawled, what URLs to crawl, and how frequently the content should be crawled. Content sources are set up and maintained in Central Administration by a Search service application administrator.

As an administrator, you can define result sources (6) based on the content available from the search index. One way to quickly understand the concept of a result source is to think of it as a reusable query. You can create result sources to specify a location from which search results can be retrieved, for example, the URL for a catalog. Or you can  specify that search results are only to be retrieved for a particular item type — for example, pictures.

One simple example might be to set the result source to include all listings that are currently valid (in other words, outdated listings never appear on the site).

Finally, the online store queries (7) the index. When the query-processing component receives a query from the search front end, it analyzes and processes the query to optimize precision, recall, and relevance. The processed query is submitted to the index component. The index component returns a result set based on the processed query to the query-processing component (which in turn processes that result set, before returning it to the search front end).

Locus IT Project Management Office
What’s it?