Application Integration Framework (AIF) Dean Wierman Lead Program Manager Microsoft Corporation

Agenda Overview Functionality Architecture

AIF Overview AIF is a response to partner and customer pain points A need for simpler, lower cost data interchange options Difficult to adapt business processes in systems Commerce gateway lessons learned Partners do not want BTS required for simple integration AxBC API set too limited to be useful Customers dislike the xCBL dependency Cumbersome error handling Does not support EAI scenarios very well today Replaces Commerce Gateway

What is AIF? Integration tool enables Business-to-Business scenarios (B2B) Orders-to-Cash Procure-to-Pay Enables Application-to-Application Integration scenarios (A2A) SDK provides Tools and Documentation Document-oriented XML-based (XSD) X++ Framework enables partners to easily extend the exposed API set

Orders to Cash and Procure to Pay Scenarios *The teal-colored boxes are not Axapta 4.0 commitments

Adapters and Interfaces Pluggable Adapter Framework (async) File System MSMQ BizTalk Server 2004 (Post 4.0 release) Outbound Web Service Adapter Custom Adapters Web Service Interface (sync)

Transaction Types Adapters (File System, MSMQ, BTS, WS) Send Documents Receive and Create Documents Respond to Read Requests Web Service Interface Request Documents from Axapta Submit Documents to be created in Axapta

Transaction Flows Send Documents Receive Documents Process Read Requests

Send Documents User activity initiates Send Framework routes document to each eligible endpoint Reads complex document from Axapta database Strips out unauthorized fields Value Maps Serializes document from Axapta class into XML Performs optional pipeline processing Value substitutions and custom processing Places document into outbound adapter Logs document into Document History

Receive Documents Document appears in inbound queue Performs security validation Processes document into Axapta Performs optional pipeline processing Value substitutions and custom processing Validates presence of required fields De-serializes document from XML to document class Validates Business Rules Writes to Axapta database Logs document into Document History

Process Read Requests Read request appears in inbound queue Performs security validation Sends document from Axapta Reads complex document from Axapta database Strips out unauthorized fields Value Maps Serializes document from Axapta class into XML Performs optional pipeline processing Value substitutions and custom processing Places document into outbound adapter Logs document into Document History

Architecture

* Post 4.0 Release

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.