CHAPTER 1: ARCHITECTURE
CHAPTER 2 : DATA DICTIONARY
CHAPTER 3 : USER INTERFACES
CHAPTER 4 : SECURITY
Lesson 4 : Architecture
Microsoft Dynamics AX has a three-tier architecture.
Microsoft Dynamics AX has Three-Tier Architecture:
Three-tier architecture is defined as having a separate database, server and client where:
- The database stores the data.
- The server runs the application business logic.
- The client application allows users to connect to the server to access business logic and use the data in the database.
In Microsoft Dynamics AX the three tiers include the following:
- A SQL Server Database that houses the data entered into, and used by, the Microsoft Dynamics AX application. It also houses the model store that contains the application elements. (Application elements are explained in the following lesson)
- An Application Object Server (AOS) is a service that runs most of the business logic. This runs continuously on a central server.
The Client application is the user interface through which an enduser accesses Microsoft Dynamics AX. There are various clients available including the Microsoft Dynamics AX rich client and Enterprise Portal.
If you understand the architecture of Microsoft Dynamics AX, you can more effectively plan, customize, and deploy the Microsoft Dynamics AX system. The topics in this section provide an overview of the Microsoft Dynamics AX system and associated components.
- System architecture
- Security architecture of the Microsoft Dynamics AX application
- Data partitioning architecture
- Component architecture
- Development environment
The Microsoft Dynamics AX solution encompasses both theMicrosoft Dynamics AX application and the Microsoft Dynamics AX application platform on which it is built. The Microsoft Dynamics AX application platform is designed to be the platform of choice for developing scalable, customizable, and extensible ERP applications in the shortest time possible, and
for the lowest cost. The following key architectural design principles make this possible.
- Separation of concerns
- Separation of processes
- Model-driven applications