Chapter 1: X++ Unit Test Framework
Chapter 2: Working with Data
Chapter 3: Classes
Chapter 4: Forms
Chapter 5: Visual Studio Integration
Chapter 6: Workflow
Lesson 1 : Architecture
Architecture in Forms:
Architecture in form supports the interaction between the user and the database. It focuses on the following actions.
- Displaying and receiving data
- Filtering data
- Sorting data
Modifying data The application and business logic are not integrated in forms but programmed on the underlying tables and classes.
A form consists of five components in the AOT:
- Data sources
Permissions All of these components have been described in previous Microsoft Dynamics AX 2012 development courses. This course goes in to more detail about the three main sections – Methods, Data sources and Design.
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
Application Object Server architecture
An Application Object Server (AOS) is a core component of the Microsoft Dynamics AX installation and is installed by using Setup. An AOS enforces security, manages connections between clients and the database, and provides the foundation where business logic for Microsoft Dynamics AX is executed. An AOS is implemented as a Microsoft Windows service. By default, an AOS is listed in the Services pane as Microsoft Dynamics AX Object Server 6.0$ InstanceName. As a Windows service, AOS works in the following ways:
- An AOS runs in the security context of either a specific domain account or the NT Authority/Network Service account, depending on the setup.
- The status of an AOS is reported to the Windows event logs. Therefore, administrators can view errors and warnings that can help them troubleshoot problems.
You can install an AOS on a single computer, together with the database, model store, and other Microsoft Dynamics AX components. Alternatively, you can install application object servers on multiple computers and group these computers in a load-balanced cluster. Because Microsoft Dynamics AX requires Windows-integrated authentication for all servers in the system, you must be running Active Directory.