Académique Documents
Professionnel Documents
Culture Documents
Recommended Infrastructure
Microsoft Dynamics AX 2012 R2
Recommended Architecture
Design
1.12
1.14
1.15
As such all specifications below are defined as virtual resources and do not necessarily map one to one to the actual
physical resources that the servers ultimately run on. Physical resources are dedicated to a virtual server only where
noted below.
Additionally, due to the virtual nature of the servers, it is relatively easy to increase (and in some cases decrease) the
allocated resources.
1.1
Document References
Document Name
Version
Author
April 2011
Microsoft Corporation
Microsoft Corporation
Microsoft Corporation
David Reinhold
Microsoft Dynamics Ax Performance and
Scalability Engineer - Database
David Reinhold
Microsoft Dynamics Ax Performance and
Scalability Engineer - Database
Microsoft Corporation
Mike Ruthruff
Applies to: SQL Server 2005
Microsoft
1.2
March 2010
Microsoft
The basic requirements (for what will enable the project to start) for the project topology below. From a conceptual
level all the solution components could be co-hosted on one server, however there are a number of constraints and
best practices that dictate this approach is not in the best interests of the project.
Constrains:
Namely, the bare bones option of a consolidated server hosting all services for the solution SQL AX,
SharePoint, SSRS, SSAS
Hardware and licensing costs could be reduced by consolidation of services, however application
component complexities and supportability issues could outweigh and cost benefit saved up front.
The consolidation of services onto one server may also introduce issues with the strategic direction
addition of any services to this one platform in the future would cause compatibility, scalability, testability,
supportability and performance issues.
1.3
1.4
There will also be a requirement for development and Test servers within Al Thuraya premises. These can be in a
single physical server or in different physical servers.
Development Server:
A virtual server with separate Application Tier and Database Tier servers as shown in above diagram. This will be
used for development or customization.
Test Server:
A virtual server with separate Application Tier and Database Tier servers as shown in above diagram. This will be
used to Test the application before deploying into Production or Live server.
Client to AOS: 100mb LAN connection with less than 5 milliseconds latency
AOS to Database: 1000mb LAN connection with less than 5 milliseconds latency
Integration Server to AOS: 1000mb LAN connection with less than 5 milliseconds latency
SharePoint to AOS: 1000mb LAN connection with less than 5 milliseconds latency
Microsoft Dynamics AX can operate on networks that use Internet Protocol Version 4 (IPv4) or Internet Protocol
Version 6 (IPv6)
1.7
Domain requirements
Computers running Microsoft Dynamics AX components must have access to other computers in the same
Active Directory service domain, with Active Directory configured in native mode.
To support e-mail alerts in Microsoft Dynamics AX, an SMTP (Simple Mail Transfer Protocol) server must be
present in the environment.
1.8
1.9
The AX 2012 Application Object Server will be used to host a single Production instance of the Dynamics AX 2012
AOS R2 Service.
All Dynamics AX transaction processing will be performed by the AOS, so it is pertinent that this server is sized
adequately to handle the following user load:
CPU Count:
Memory:
OS:
LAN:
Disk:
Software:
1.11
The SQL database server will be used to host the Dynamics AX 2012 R2 Application database and associated model
database.
The specification below is an indication and we have not gone through any capacity planning exercises to base the
below specification on it is an indication based on our anticipated load on the server e.g. one of the items
considered was the future (near real-time) integration with the Manufacturing System.
CPU Count:
Memory:
OS:
SQL:
LAN:
Disk:
Note
When running on a virtualized environment it is pertinent to ensure that the virtual hard drives are deployed on the
underlying physical drives as to reduce/eliminate any contention on the physical drives IO capabilities.
4+
64GB
Windows Server 2012 Enterprise Edition (x64)
SQL Server 2008 R2 Standard Edition CU3 or later required (x64)
LAN:
Disk:
4+
32 GB
Windows Server 2012 Enterprise Edition (x64)
Windows terminal services
C: 75GB (OS only)
D: 60GB
Microsoft .NET Framework 3.5 SP1 (Certain AX components require .NET 4.0. These are highlighted in the AX
2012 R2 System Requirements document)