1. Dynamics AX Technical Overview Application Architecture Dynamics AX Technical Overview

2. Application – Layer Technology AXAPTAOBJECTINDEXAXAPTAOBJECTINDEX SYSTEM: Standard Application (axSYS.aod) SYSTEM: Patch (axSYP.aod) SOLUTION: Integrated Certified Solutions (axGLS.aod) SOLUTION: Patch (axGLP.aod) DISTRIBUTOR: Country Specific General Functionality (axDIS.aod) DISTRIBUTOR: Patch (axDIP.aod) LOCAL: Country Specific Integrated Certified Solutions (axLOS.aod) LOCAL: Patch (axLOP.aod) BUSINESS: Vertical Solutions made by Business Partners (axBUS.aod) BUSINESS: Patch (axBUP.aod) PARTNER: Business Partner’s Layer for Customer Specific Functionality (axVAR.aod) PARTNER: Patch (axVAP.aod) CUSTOMER: Customer’s own Modifications for the Entire Corporation (axCUS.aod) CUSTOMER: Patch (axCUP.aod) USER: Site Specific Modifications for One Customer Site (axUSR.aod) USER: Patch (axUSP.aod) The kernel drives the application

3. N-tier Logical Architecture 3-tier (fat) Database (SQL Server, Oracle) Application (Kernel and AOD) Database Driver (ODBC) Application Processing (All) Presentation (Axapta Client) 3-tier (thin) Database (SQL Server, Oracle) Application (Kernel and AOD) Database Driver (ODBC) Application Processing (Client Only) Presentation (Axapta Client) Axapta Object Server (AOS) Axapta Object Server (AOS) Network

4. 3-tier implementation Introduces the AOS to manage the AOD (Axapta Object Database) 3-tier (Thin) – First Time Object is accessed it is downloaded to the client – When printing, only records accessed are downloaded, the print is created locally – Allows low client bandwidth – Lower requirements for client machines – Requires Additional server capacity – Provides high level of database security 3-tier (Fat) – Similar to 2-tier client except that it gets application elements from the AOS – Requires high bandwidth to the SQL server – Puts very little load on the object server – Good for developers, batch jobs

5. 3-tier Physical model

6. Axapta Object Server (AOS) Allows mix of both thin and fat clients You can have separate AOS instances for each of your applications Runs as a windows service spanning additional processes for each application instance AOS Load Balancing – For Scalability in large system, multiple AOS servers can be clustered with Axapta’s built in clustering software – Cluster is formed dynamically so adding or removing servers is easy

7. Axapta Client Same client operates in either 3-tier (fat), or 3-tier (thin) mode Axapta Clients do not load the network just because the user is interacting with the application Client concurrency on WAN is greatly improved using the client in 3-tier mode AOS clients will benefit from extra available bandwidth

8. Axapta Web Applications - Firewall Users can access Axapta Web Application in your DMZ Communication from IIS Web Application server to Axapta Object Server is done via Axapta.NET Connector through inner firewall

9. Database Uses standard SQL syntax RDBMS can be either MS SQL Server or Oracle Uses ODBC for DB communication The AOS improves performance by sharing: – Record Caching – SQL Connections – Cursors Can be clustered in Active / Passive configuration for redundancy

10. Client Deployment Flexibility

11. Rich Client - Traditional Web Deployment Terminal Server Web Applications Handheld

12. Rich Client Most efficient interface for heavy users

13. Web Deployment – Zero Administration The Axapta Web Deployment Client – Easy deployment of Axapta – Through Internet or Intranet – Install options pre-defined – ActiveX Component – Indicates state of local installation – Will install or upgrade local installation (button will indicate this)

14. Web Deployment Client Use it with ordinary web content, Active Desktop content or in any ActiveX capable document/container Activating this control (by clicking on it) the user's machine is investigated to find out: – Whether or not a Axapta installation is present on his machine – If not, a Axapta client is downloaded from a server through the Internet – If the WDC finds an installation on the user's machine, it checks if the server contains a service pack that is not installed – If so, it is installed on the user's machine – Finally, the Axapta client is launched

15. Terminal Server Terminal server can be used to further increase your architecture flexibility Allows you to centralize application management and deployment (Launch Folder) Can be distributed as a desktop, as a single application or as an embedded web app

16. Upgrading Service Packs and Hot Fixes

17. Upgrading - Overview Delivered as Service Packs or Major Releases Previous customized processes are preserved during upgrade The Version-layer technology lets you monitor what has been changed, where it was changed, and from where changes originated. Built-in tools for creating upgrade projects, comparing, and merging objects.

18. Upgrading - How it works SYS Layer VAR Layer Table ATable BTable C Class MClass N Form XForm YForm Z USR Layer Customized AxaptaService Pack from MBS SYP Layer Table BTable DTable E Class O Form AForm Z

19. Upgrading - How it works (cont.) SYS Layer VAR Layer Table ATable BTable C Class MClass N Form XForm YForm Z USR Layer Service Pack Applied SYP Layer Table BTable DTable E Class O Form AForm Z Overlapping objects are now compared and merged to VAR layer

20. Upgrading – How it works (cont.) SYS Layer VAR Layer Table ATable BTable C Class MClass N Form XForm YForm Z USR Layer Upgraded SYP Layer Customized objects updated with service pack changes