Microsoft Dynamics AX 2012 R3 technical features. Microsoft Dynamics AX 2012 R3 technical features.
There are some major changes in AX 2012 R3 as follows1.Automated deployment of AX 2012R3 in Windows Azure2.Building Microsoft AX services integration with the Microsoft Windows Azure Service Bus3.Data synchronization to multiple instances of Microsoft Dynamics AX4.Optimizing the performance of Microsoft Dynamics AX deployment5.Create Microsoft Dynamics AX builds using the new X++ server-side parallel compiler
IaaS(Infrastructure as a service), as the name suggests, provides you the computing infrastructure, physical or (quite often) virtual machines and other resources like virtual-machine disk image library, block and file-based storage, firewalls, load balancers, IP addresses, virtual local area networks etc. Examples : Amazon EC2, Windows Azure, Rackspace, Google Compute Engine.
PaaS(Platform as a service), as the name suggests, provides you computing platforms which typically includes operating system, programming language execution environment, database, web server etc. Examples : AWS Elastic Beanstalk, Windows Azure, Heroku, Force.com, Google App Engine.
While in Saas(Software as a service) model you are provided with access to application software's often referred to as on-demand software's. You don't have to worry about the installation, setup and running of the application. Service provider will do that for you. You just have to pay and use it through some client. Examples : Google Apps, Microsoft Office 365.
Although Azure does many of the configuration tasks automatically, there are a number of post-deployment actions we need to follow up after each setup. The following describes the steps needed after deployment
How the Microsoft Dynamics AX compiler works
The following is the architecture for the current compiler Microsoft Dynamics AX the build performance is affected by the metadata moving from the client to the server metadata. In addition, the long compiling times are due to the deserialization of metadata and in memory cache.
R3 Compiler Improvements Microsoft Dynamics AX the build performance is affected by the metadata moving from the client to the server metadata. In addition, the long compiling times are due to the deserialization of metadata and in memory cache.
Parallel Execution different levels on an organization, this is built on top of the existing security framework (i.e. Production cannot import HR data).
System Configuration Data: BI-Analysis and Reporting Services, Project Server Integration, EP, Batch Settings, Number Sequences, Email Parameters, AIF, System Service Accounts.DIXF Import ProcessThe import Process us done by using an abstraction layer that uses SSIS behind the DIXF framework. Within this abstraction layer, we can add possible X++ customizations.I asked the question on what would be the recommendation for migrating data from legacy systems – the following is what I could get from their recommendation (I was taking notes).There are two types of data migration architecture that consolidate both importing and cleansing data.The first option is to have a middle tier that can process the data from a legacy system, to an external system and clean it before it goes to Microsoft Dynamics AX.