AOS architecture [AX 2012]
Updated: February 1, 2013
Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
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.
Clients communicate with an AOS by using remote procedure calls (RPCs), Windows Communication Foundation (WCF), or AOS services. In previous releases, other components and third-party programs could communicate with an AOS by using either .NET Business Connector or Application Integration Framework (AIF). For this release, we recommend that third-party programs use AOS services to communicate with AOS.
The following diagram shows the AOS architecture.
Announcements: To see known issues and recent fixes, use Issue search in Microsoft Dynamics Lifecycle Services (LCS).