Three tier architecture of Microsoft Dynamics Ax (Axapta)

In Microsoft Dynamics Ax, there is a 3-tier infrastrcuture with,
  1. a database server
  2. an application object server (AOS)
  3. and a client.
The following illustration shows the three-tier architecture:

Three-tier architecture of Dynamics Ax

Few Advantage of tier architecture are as below:
  • when we seperate the application data from the application objects, it is easier to distribute upgrade versions of your application. This is because you can distribute forms, queries, classes and reports that are based on the same set of underlying tables without affecting application data.
  • Seperate data from other application objects can reduce network load.
  • You can use the AOS for sharing objects and information to multiple clients as an effective tool to increase performance.
Note: We can always install all the above three listed in a single computer - Single box setup. Or choose to install seperately the Database server, the Application Object server and multiple clients, all connected to the Database and Application server. - Multi box setup.

Comments

Mittal Mehta said…
Hi Ajit,

I am working as a configuration manager and our new project is on AX 2012.
I know there is one .xpo file for axepta db. I have some questions.

I need your help to understand.

Mittal
April 25, 2016 at 11:19 AM
Ajit said…
Hi Mittal,
Please post your questions to me. Thanks. //Ajit.
July 20, 2016 at 10:31 AM
Post a Comment

Popular posts from this blog

D365FO - Copy of databases across environments

Image
When working with Dynamics 365 Finance and operations implementations, it is an obvious step to perform database movements across environments. We have been doing this in the previous version (AX2012) as well, where we had to change the environments related settings after the database copy manually. Now we D365FO , we might end up in different scenarios based on the Tier-level of the environment . So I have tried to identify the #4 major scenarios in here and share the approach I have used.  Copy of DB from Tier 1 env. to another Tier 1 env. Copy of DB from Tier 1 env. to a Tier 2 env. Copy of DB from Tier 2 env. to another Tier 2 env. Copy of DB from Tier 2 env. to a Tier 1 env. The below picture is an illustration of different types and corresponding solutions on a high level (sorry for my not-so-good-handwriting 😅) #1 Tier 1 -> Tier 1 DB copy:   This scenario can happen quite common if you have multiple tier-1 environment in your on-going project li...
Read more

Extended Data Types in Microsoft Dynamic Ax & EDT array

Image
·          An extended data type is extended from a base type or another extended data type. The difference is that an extended data type has a property sheet where information such as labels, length and left or right adjustment are stored. ·          EDT are a central part of MorphX. Whether you are adding fields to a table or declaring variables from X++, extended data types should always be used instead of using base types and the reason for that is Dynamics Ax provides powerful features to handle EDTs. ·          The best practice is to check before creating a new extended data type you should check whether in existing one will fulfill your needs. ·          If you have found an EDT which suits your needs, but another label or help text is required, you should create a new EDT with your requirements, but never mod...
Read more

Error: Field 'xxx' does not exist in D365Ops

Image
Today I encountered a weird error while working with newly created Enums and Tables in Visual Studio 2015 with a Dynamics 365 for Finance and Operations project. Error message while trying to build my project was: The underlying type 'BKA_Status ' or its base type for table 'BKA_GoalMaster' field 'GoalStatus' does not exist. The underlying type 'BKA_GoalTypes ' or its base type for table 'BKA_GoalMaster' field 'GoalType' does not exist.</Message> However, I had the 'BKA_Status' as well as 'BKA_GoalTypes' Enums already available in my project and even the project is Synchronized with the database. Root cause: To be honest, I was unable to find the root cause for sure. However, I imagine the error has something to do with the refresh of metadata because of the kind of solution which helped to resolve the error.  I have had 'Extends' property filled in with another Enum which was not existing in t...
Read more