22.04.2008, 03:25 | #1 |
Участник
|
Dianne Siebold: AIF Top Ten
Источник: http://blogs.msdn.com/dsiebold/archi...f-top-ten.aspx
============== AIF Top 10 in Dynamics AX 2009 You’ve probably already heard that the release of the new version – Dynamics AX 2009 – is on the horizon. For those of you who are using AIF or are planning to use it, the next version has some great features. Here is my list of the top 10 AIF features in Dynamics AX 2009.
An AX service can be consumed internally by X++ code or you can expose that service externally through Web services. Now, you also have the ability to consume an external Web service from X++ code and access the service operations through Intellisense.
When you use one of the transports such as BizTalk or the file system to exchange data, AIF uses the document services internally. You can also expose the document services externally as Web services. When exposed as Web services, the document services support WCF.
Dynamics AX now ships with a default endpoint. This means you can get data exchanges up and running without having to configure a specific endpoint. When you send a message into AX and you want to use the default endpoint, only the action is required to be specified in the message header. You no longer have to specify the SourceEndpoint, SourceEndpointUser, or DestinationEndpoint elements in the message. When AIF uses the default endpoint, it verifies that the user sending the message has the appropriate security. The way the user information is retrieved depends on the transport method. For example, if you use the file system, AIF considers the file owner as the submitting user. Of course, you can still set up specific endpoints when you want to specify the endpoint users, specify endpoint constraints, and implement other functionality that’s only available to specific endpoints
This means that all the configuration options available for WCF services are available for the document services and any service in AX. This also means that Dynamics AX services can be implemented as part of your overall SOA strategy. Look here for an illuminating discussion of the advantages of WCF services.
Services are now an integral part of AIF and are the external interface for business logic in AX. You can also consume a Web service from X++ with full IntelliSense support. You simply add a service reference and the service is available to you in the code editor. What does this mean for me, you ask? This translates into a whole new world of integration scenarios. For example, you cou ld build functionality that takes item information (quantity, weight, size, and so on) from a form, calls a Web service, and then presents various shipping methods and costs to the user. If a Web service that calculates tax amounts was available, you could embed that functionality directly into a form in AX. Powerful stuff, I say.
Setting up the batch is as easy as (1) adding the batch job, (2) adding some tasks to it (one for each of the four AIF message processing classes), and (3) changing the status to Waiting. You can modify each task so that it’s dependent on the completion of the previous task so that the tasks execute in the proper order.
The data objects have a programmer-friendly interface and implement XML serialization and de-serialization. The document object is the top-level data object so technically it is also a data object. Using these data objects is much easier than coding the XML string, ensuring that it validates against the message and documents schemas, and so on. For example, AIF would generate three data objects to represent the Customer document:
· A default project in the AOT containing all the classes and objects created by the wizard. · An AOT node for the service · An AOT node for each service operation that the service supports.. · The service class, the document class, and the data object classes – The actual classes that encapsulate the data exchange business logic. Found in the Classes node in the AOT. · A macro that contains all the data types for the data objects referenced by the service class. · AxBC (Ax) classes that provide an object API on top of the database tables referenced in the query. · A job that generates the schema for the service class. Источник: http://blogs.msdn.com/dsiebold/archi...f-top-ten.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
Теги |
aif, axbc |
|
|