Deployment topologies for Retail [AX 2012]
Updated: February 20, 2013
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack
The following table lists the types of computers that are used in a typical Retail deployment.
Types of computers
With the exception of the communications server, the computers at the head office are all standard in a Microsoft Dynamics AX deployment. Depending on the requirements of your organization, a particular computer can be used for more than one of the purposes in the previous table. We recommend that you load balance across multiple computers whenever load balancing is possible.
Typically, head office and store computers on which Synch Service is installed also have SQL Server Express Edition installed. However, this instance of SQL Server is used only for the Synch Service message database.
For development and testing, you can install the complete Retail system on a single computer. However, a deployment of this kind is not a supported production scenario.
The following figures illustrate typical deployment topologies for a POS system.
Each component of a POS system is hosted on a dedicated computer
In Figure 1, each component is hosted on a dedicated physical computer or virtual machine. Components that support multiple instances, such as AOS and Synch Service, could be installed on additional computers for load balancing. This deployment topology is appropriate for a large retailer.
Figure 1 Hosting of Retail POS components on dedicated computers
POS components are hosted on shared servers
In Figure 2, on the head office side, the Synch Service instance, Real-time Service, and Enterprise Portal for Microsoft Dynamics AX have been combined on a single computer. A midsize retailer might want to consolidate these services on one computer or run them on virtual machines on a single physical server. On the store side, Synch Service is installed on the same computer as the store database server.
Figure 2 Shared hosting of Retail POS components
Store-side database topologies
Retail supports the following store-side database topologies:
POS registers have offline databases that are synchronized with the store database when the POS registers are connected.
POS registers do not have databases and must always be connected to the store database.
Figure 3 illustrates the two supported topologies. In the POS portable topology, the POS register uses the store database by default, and synchronizes its local database and the store database. If the store database becomes inaccessible, the POS register uses its offline database until the connection to the store database is re-established. In the POS always online topology, the POS register must always be online to connect with the store database.
Figure 3 Supported database topologies for Retail POS registers
Synch Service and Real-time Service have been omitted from Figure 3, because they are not affected.
The following figures illustrate typical deployment topologies for an online store system.
Each component of an online store is hosted on a dedicated computer
In Figure 4, each component is hosted on a dedicated physical computer or virtual machine. Components that support multiple instances, such as AOS, Synch Service, and online store sites, could be installed on additional computers for load balancing.
Figure 4 Hosting of Retail online store components on dedicated computers
Online store components are hosted on shared servers
In Figure 5, Synch Service, Real-time Service, and Enterprise Portal have been combined on a single computer. A midsize retailer might want to consolidate these services on one computer or run them on virtual machines on a single physical server.
Figure 5 Shared hosting of online store components