Ecommerce Deployment

Ecommerce Deployment : This lesson explores the omni-channel deployment topology considerations for the Microsoft Dynamics AX 2012 for Retail and the server roles for the Microsoft Dynamics AX 2012 for Retail components for the head office and the SharePoint Server 2013 farm for the online store.

Lesson Objectives

The objective is to explore the Ecommerce deployment topology considerations in Microsoft Dynamics AX 2012.

Omni-Channel Topology

The following diagram illustrates a high-level view of the omni-channel deployment topology, including both online and brick-and-mortar stores. Depending on the business requirements for the Ecommerce solution, the deployment may include a number of data centers, for example, located in different geographies such as Americas, Europe, and Asia. The following diagram illustrates the deployment topology with multiple online store datacenters.

The following diagram illustrates the logical infrastructure architecture and the main server roles for the Ecommerce solution implementation

Ecommerce Infrastructure Architecture

The following diagram illustrates the logical infrastructure architecture and the main server roles for the Ecommerce solution implementation. The infrastructure architecture diagram shows the Microsoft Dynamics AX 2012 for Retail components for the head office and the SharePoint Server 2013 farm for the online storefront. The following table describes the server roles that are shown in the diagram.

Head Office Infrastructure Considerations

When you deploy Microsoft Dynamics AX Ecommerce solution, you must have a clear understanding of your organization’s or customers’ requirements so that you can make good decisions as you plan the solution implementation. You need to carefully consider the performance requirements for your deployment during the planning stage, to guarantee that the deployment is successful. This section provides an overview of the hardware infrastructure considerations for AX deployment in the head office.

Based on the performance requirements, the server components in the head office support scale-out options of either clustering or multi-instance. For the smaller implementations, you can also combine multiple components on the same server.

You must consider a number of factors when you plan the hardware infrastructure for Microsoft Dynamics AX deployment in the head office. This includes the total average number of transactions that are processed per work hour. The transactional volume is a key factor for planning your hardware and software components, such as the following:

• The database server infrastructure, such as the type and number of drives
• The number of Application Object Server (AOS) clusters
• The number of AOS instances in a cluster
• The number of batch servers
• Network capacity