Whether it's upgrade time for you, or you're just implementing AX for the first time, integrating with other applications, within your business our externally, is going to be a big part of your project plan.
There are at least 2 ways to implement integrations architecture in your Dynamics environment and they are..
The 2009 AIF, Application Integration Framework, is the one provided out of the box, kind of, some assembly required of course. It has advanced since the AIF of version 4 and the Business (COM) Connector of 3.0 and earlier, but still highly dependent on AOT side coding and synchronization and not very developer friendly.
Number 2 is the Microsoft.Dynamics Framework and C#, Object based programming, and the old inheritance model. This is a powerful, flexible platform to build sturdy integrations, or complete applications for that matter, and it will be the topic of the next several posts.
The sections I will cover in the upcoming posts are..
1) Understanding the Dynamics AX data schema and exposing it via SQL Server.
2) Generating Object Model classes based on your Dynamics AX data schema in C#.
3) Building generic Foundational Service Architectures in C#.
4) Coding the Data and Business classes and building a test application.
Thanks, and I'll be back real soon.
H
Subscribe to:
Post Comments (Atom)
Hi Harold,
ReplyDeleteHave you got any updates on this?
I am interested in the code generation part of this.
Regards,
Shashi
I am using the DAX Object / Collection in all of my production AX integrations and external apps now, and it has proven to be very reliable and stable, but I am starting to move it toward LINQ, so thats what I will start covering. If anyone wants information on the object model / generation solutions, I may revisit it as time permits.
ReplyDelete