other applications:
• Services and the Application Integration Framework: Services
are the preferred option for integration with Microsoft Dynamics
AX. Services in Microsoft Dynamics AX are used to expose its
functionality through WCF-based services. Microsoft Dynamics AX
code and external applications can consume Microsoft Dynamics AX
services. AIF supports the processing of inbound and outbound
messages such as 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 interop to X++: You can use the .NET interop to X++ feature
to call X++ code using C# or another managed language. A proxy is
an automatically generated .NET class, in C# or another managed
language, that mimics an X++ class of Microsoft Dynamics AX.
• .NET interop from X++: The .NET interop from X++ (also known
as the CLR Interop in the previous release) provides interoperability
with external .NET components and you can execute managed-code
components from within X++ code. .NET interop from X++ is useful
when you want your X++ code to access functionality provided by a
CLR-managed assembly. This includes assemblies that are installed
with the .NET Framework and any assemblies that you create with a
language such as C# or Visual Basic.NET.
• Consume external web services: You can use the Microsoft
Dynamics AX programming model to consume external web
services from within X++ code. To consume an external web service
from X++, you must first create a reference to the web service. After
creating a reference to the web service, you can invoke it from X++
and view the available methods with IntelliSense. Calling and
managing external web services is done completely within Microsoft
Dynamics AX.
The following figure shows how the AIF integration components interact with
Microsoft Dynamics AX through the AOS.
Regards,
Hossein Karimi
No comments:
Post a Comment