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 4: Commerce Runtime
Commerce Runtime : This lesson discusses the Commerce Runtime and its components.
To objective is to describe Commerce Runtime architecture and components
The Microsoft Dynamics AX Commerce Runtime (CRT) component serves as the intermediary between Microsoft Dynamics AX and an online store. It provides an engine for a retail channel and enables delivery of content and retail services in a scalable way.
Commerce Runtime provides a set of assemblies that connect to the CRT database that stores business data for the online store. CRT assemblies also use the CDX Real-Time Service to connect to Microsoft Dynamics AX.
Commerce Runtime contains a data access layer, a services layer, a workflow layer, and an API layer:
- Data access layer
A data access layer sits on top of the CRT database. In the data access layer, raw data is translated into objects in memory. For example, an object could be a product. Products have attributes like price and color. The data access layer has functions you can use to manipulate these objects. Stored procedures pass packets of data from the database to data entities that can be used in services and workflow. You can update the packets of data to include new fields that you add in Microsoft Dynamics AX. On top of the data access layer is a services layer. Services query for real time data. You can use these services to customize existing functionality or add your own services with new functionality.
- Workflow layer
On top of the services layer, there is the workflow layer. A workflow is a collection of services and business logic that together define business processes. For example, when a customer adds an item to the cart, you could use workflow to get the price, perform validation, check inventory quantity, calculate shipping, calculate tax, and calculate discounts. You can use workflows that are included in Microsoft Dynamics AX, or you can create new workflows. You can also use a workflow to connect to a third-party system as part of your business processes.
- Application Programming Interface (API)
On top of the workflow layer is the API layer. You can use the API for things like getting information about items, price calculation, shipping calculation, and placing orders. You can extend the API to fit your business processes.