Module 1: INTRODUCTION AND COURSE OBJECTIVES
Microsoft Dynamics AX 2012 R3 for Retail in eCommerce Stores: Installation and Configuration
Module 2: ECOMMERCE ARCHITECTURE
Module 3: INSTALLING ECOMMERCE COMPONENTS
- Lesson 1: Pre-installation Tasks
- Lesson 2: Deploy Retail Online Channel and Configure Settings
- Lesson 3: For Server Farm: Configure Settings in the oob-topology.xml File
- Lesson 4: Execute PowerShell Scripts to Deploy and Configure Online Store
- Lesson 5: Verifying the Retail Online Store Deployment and Troubleshooting
Module 4: ONLINE STORE SET UP AND PUBLISHING
- Lesson 1: Setting up Online Store Integration
- Lesson 2: Creating Online Store Navigation Structure
- Lesson 3: Creating and Configuring Online Store
- Lesson 4: Configuring Data Distribution and Publishing an Online Store
- Lesson 5: Managing and Publishing Online Store Products
- Lesson 6: Setting Up Shipping Charges for the Online Store
Module 6: ECOMMERCE DEPLOYMENT TOPOLOGY
Lesson 2: Online Store Topology
Online Store Topology
Online Store Topology : The online store is a search-driven site that uses SharePoint 2013 search technology to dynamically show content. This lesson begins with the overview of search components before covering the server roles that are included in the online store topology. Then, this lesson discusses the sample online store topologies and hardware sizing, and provides the high-availability and performance considerations for planning your online store deployment.
The objective is to provide reference and examples to help you plan the topology for your online store implementation.
The search architecture in SharePoint 2013 contains a number of search components and databases. SharePoint 2013 search components are as follows:
- Crawl component
- Content-processing component
- Analytics-processing component
- Index component
- Query-processing component
- Search administration component
The crawl component crawls the content sources. You can crawl lots of content sources, for example file shares, product catalog, and SharePoint content. To retrieve information, the crawl component connects to the content sources by invoking the appropriate indexing connector or protocol handler. After retrieving the content, the crawl component passes crawled items to the content-processing component.
The content-processing component processes crawled items and sends these items to the index component. The content-processing component performs operations such as document parsing and property mapping. It also performs linguistics processing such as language detection and entity extraction. The component transforms crawled items into artifacts that are included in the search index. The content-processing component also writes information about links and URLs to the link database.
The analytics-processing component performs two types of analyses: search analytics and usage analytics. This component uses information from these analyses to improve search relevance, create search reports, and generate recommendations. Search analytics is about extracting information, such as links, the number of times an item is clicked, anchor text, data related to people, and metadata, from the link database. This information is important to relevance.
Usage analytics is about analyzing usage log information received from the front-end via the event store. Usage analytics generates usage and statistics reports. The results from the analyses are added to the items in the search index. In addition, results from usage analytics are stored in the analytics-reporting database.