Integration with Microsoft Dynamics AX [AX 2012]
Updated: May 25, 2012
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012
There can be benefits to integrating your Microsoft Dynamics AX application with other technologies. One benefit is you can use other technologies to develop parts of your overall Microsoft Dynamics AX application. For example, you can write some of your functions in C# instead of in X++, and then integrate your Microsoft .NET Framework assembly into Microsoft Dynamics AX.
Another benefit from integration is the ability to coordinate your Microsoft Dynamics AX application with external applications. The external applications can be inside or outside the boundary of your enterprise. The functionalities of the two applications can interact, and data can be exchanged.
You can integrate your Microsoft Dynamics AX application by using the following technologies:
Services and Application Integration Framework (AIF) – Exposes business logic to other internal or external systems. Microsoft Dynamics AX supports integration with the Application Integration Framework (AIF) components using the services programming model. Microsoft Dynamics AX can expose its functionality through services that are based on Windows Communication Foundation (WCF). Microsoft Dynamics AX code and external applications can consume Microsoft Dynamics AX services. AIF supports the processing of inbound and outbound messages. This processing includes message transforms and value lookups. Together, services and AIF provide the programming model, tools, and infrastructure support for XML-based integration with external applications and data.
.NET Business Connector – Enables external applications to access Microsoft Dynamics AX data and invoke business logic.
.NET Framework – Enables X++ code to call methods in assemblies that are managed by the common language runtime (CLR). Also provides proxy classes generated as C# or Visual Basic source code for X++ classes in Microsoft Dynamics AX. Your C# code can call the proxies and use them much as an X++ class would call other X++ classes directly. You generate the proxy classes by using Microsoft Visual Studio.
To apply advanced criteria to your search for Help about Microsoft Dynamics AX, use the WebSearchAx tool.
To support a range of options for customization and programmability, Microsoft Dynamics AX provides the following types of services:
Custom services are services that you create to expose X++ logic through a service interface. You can use the business logic with inbound or outbound transfers.
Document services represent data and business logic within Microsoft Dynamics AX. You can use or customize standard Axd document services that are included with Microsoft Dynamics AX. If none of the standard document services meet your needs, you can create a new document service by using the AIF Document Service Wizard.
System services cannot be customized. The Query Service, Metadata Service, and User Session Service are WCF services included with Microsoft Dynamics AX. System services provide the following:
Access to data that is returned in AOT queries.
Metadata for AOT objects such as tables and extended data types (EDTs).
Data about the calling user, such as default language and default company.
For more information about integration with services and AIF, see Services and Application Integration Framework (AIF).
The Microsoft Dynamics AX .NET Business Connector enables external applications to access Microsoft Dynamics AX data and invoke business logic.
The .NET Business Connector provides interoperability with the .NET Framework. Use these components for integration with external applications that are written in managed code and which are built with the .NET Framework. The .NET Business Connector requires the installation of the Windows Server SDK. For more information about .NET Business Connector, see .NET Business Connector Overview.