Table of Contents
1. Introduction 3
2. Executive Summary 4
2.1. Overview 4
3. Software 5
3.1. Introduction 5
3.2. Dynamics AX 5
3.2.1. Application Integration Framework 5
3.2.2. Web Service 5
3.2.3. .NET Business Connector 6
4. Interface 7
4.1. XML 7
4.2. MSMQ 7
4.3. CLR Interop 7
4.4. COM 7
1. Introduction
This document outlines different integration techniques between any third party software and Dynamics AX V4.0. Consultants from Systems Advisers Group (hereafter SAG), can assist in implementing the integration.
This document has been generated in order to:
o Assist in explaining Microsoft Dynamics Ax integration technique methods.
o Give a better understanding of how AX to be integrated.
2. Executive Summary
2.1. Overview
This proposal is intended to impart our knowledge of the Microsoft Dynamics AX product, especially regarding the potential for systems integration. In particular SAG will focus on the Microsoft preferred methodology for integrating disparate systems and entities to Microsoft Dynamics AX.
This document will highlight:
· Standard Microsoft features for integrating with Microsoft Dynamics AX.
- Software
3.1. Introduction
This section will give a brief high level overview of Microsoft Dynamics AX and the different integration techniques there are.
3.2. Dynamics AX
Microsoft Dynamics AX is a hugely flexible and well developed product for companies in an International Environment. Version 4.0 release brings new and improved functionality to the product including:
o Deep Microsoft integration including:
o Windows 2003, SQL 2005 reporting services, SharePoint
o Outlook Style User Interface
o Global Solution, Global Reach
o Regional Functionality
o Improved Intercompany functionality
o .net web services
o Complete Solution
o Advanced Alerts
o Microsoft supported Industry Builder Solutions
o Improved developer platform for company development
o Performance and Security
3.2.1. Application Integration Framework
The Application Integration Framework (AIF) is a new document based integration technology. It contains both a rich development environment and a robust execution model. As mentioned above, there are several integration [XML] documents delivered as part of the base system.
AIF supports BizTalk Server 2006, Microsoft Message Queue (MSMQ), and file system adapters that are well suited for asynchronous data exchange. The framework also supports a Web Services interface that is well suited for synchronous data exchange. There is also, of course, the ability to create custom adapters.
3.2.2. Web Service
Microsoft Dynamics AX can use XMLHttpRequest object (Microsoft.XMLHTTP) to send an arbitrary HTTP request, receive the response, and have the Microsoft XML Document Object Model (XMLDOM) parse that response.
This object is integrated with MSXML to support sending the request body directly from, and parsing the response directly into, the MSXML Document
Object Model objects. When combined with the support for XSL, the XMLHttpRequest component provides an easy way to send structured queries to HTTP servers and efficiently display the results with a variety of presentations.
3.2.3. .NET Business Connector
Business Connector enables third-party applications to interface with Microsoft Dynamics AX as though they were a native Microsoft Dynamics AX client. Applications built using the Microsoft .NET Framework or ASP.NET can now interface with Microsoft Dynamics AX using the .NET Business Connector. The .NET Business Connector is integrated with Enterprise Portal and Web services.
Authentication
To support integration with Microsoft Windows Services and to enhance product security, the .NET Business Connector requires Windows integrated authentication.
Benefits of .NET
The .NET Framework enables developers to build and run all kinds of software, including Web-based applications, smart-client applications, and XML Web services. The .NET Framework is composed of the common language runtime and a unified set of class libraries. The framework supports more than 20 programming languages.
The .NET Business Connector (Microsoft.Dynamics.BusinessConnectorNet namespace) provides the following managed classes:
Axapta
AxaptaBuffer
AxaptaContainer
AxaptaObject
AxaptaRecord
VariantWrapper
Each class has several methods.
- Interface
4.1. XML
Movement of data can be held in XML messages. SAG will require an XSD Schema for all XML message used. SAG can assist with creation of XSD Schema.
4.2. MSMQ
Message Queuing provides guaranteed message delivery, efficient routing, security, and priority-based messaging. As part of the internal transaction support, Microsoft Message Queue (MSMQ) provides specific functionality to handle cases where an MSMQ application wants to send only a single message in a single transaction.
Microsoft Dynamics AX has built in wrappers around the MSMQ components that support queue lookup, queue management, message management, queue administration, and transaction support.
4.3. CLR Interop
The CLR Interop feature enables X++ developers to add CLR assemblies to the Object Tree within Dynamics AX and to write X++ code that interoperates with objects in these assemblies.
4.4. COM
The Microsoft Dynamics AX Business Connector is Microsoft AX's way of offering the componentsin Microsoft Dynamics AX to the outside world via the COM standard. This means thatcomponents found in Microsoft Dynamics AX are seamlessly accessibleto any application supporting the COM standard. These applications can be written in avariety of programming languages: Visual Basic, C++, Java, etc. The Microsoft Dynamics AX Business Connector does not add any additional functionally to the Dynamics AX components, but simply exposes the components tonon-Microsoft Microsoft Dynamics AX applications, allowingthe programmer to leverage existing Microsoft Dynamics AX functionality.
Any inbound interfaces will interact with Microsoft Dynamics AX business connector (COM component). To update Microsoft Dynamics AX database, Microsoft Dynamics AX must be used.
The Microsoft Dynamics AX COM object uses the IMicrosoft Dynamics AX interface.
The IAxapta3 Interface has the following identifiers:
IID (interface identifier):
IID_IAxapta3 = {481A6197-958C-4DDE-B714-DEAD44E3E867}
CLSID (class identifier):
CLSID_Axapta3 = {71421B8A-81A8-4373-BD8D-E0D83B0B3DAB}
ProgID (programmatic identifier):
AxaptaCOMConnector.Axapta3.1
Version-independent progID:
AxaptaCOMConnector.Axapta3
Methods :
CallJob
CallStaticClassMethod
CallStaticClassMethodEx
CallStaticRecordMethod
CallStaticRecordMethodEx
CreateBuffer
CreateContainer
CreateObject
CreateObjectEx
CreateRecord
CreateReference
ExecuteStmt
ExecuteStmtEx
GetObject
GetReference
Logoff
Logon
Plus many more
3