• Enforces security, manages connections between clients and the database, and provides the foundation where business logic for Microsoft Dynamics AX is executed.
• Is implemented as a Microsoft Windows service. By default, an AOS is listed in the Services pane as Microsoft Dynamics AX Object Server 2012$InstanceName.
• As a Windows service, AOS works in the following ways:
o An AOS runs in the security context of either a specific domain account or the NT Authority/Network Service account, depending on the setup.
o 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 .NET Business Connector or Application Integration Framework (AIF). For this release, the recommendation is for third-party programs to use AOS services to communicate with AOS.
Regards,
Hossein Karimi
No comments:
Post a Comment