Configuring document exchanges

Dynamics AX 4.0

You configure document exchanges differently for asynchronous, adapter-based exchanges than for synchronous exchanges that use inbound Web services. Adapter-based exchanges include outbound Web services. These asynchronous exchanges are set up to process messages in queues using Microsoft Dynamics AX batch jobs. Inbound Web services require you to set up and configure IIS and an application integration server on your system to enable the synchronous data exchange.

Setting up the Application Integration Framework (AIF) for document exchange involves one or both of the following tasks:

  • Set up transport adapter-based exchanges (A transport adapter is a software component that enables an asynchronous exchange, in which documents are placed in queues to await processing by different transport mechanisms. To start and stop processing in the queues you use the batch functionality in Microsoft Dynamics AX. Examples include using Microsoft Message Queuing (also known as MSMQ), outbound Web services, or the file system for the exchange.).


    A transport adapter is a software component that enables an asynchronous exchange using a particular transport mechanism. Header information is added to XML documents to create messages, and these messages are placed on queues for processing by AIF services.

  • Set up exchanges that expose Web services for inbound document transfer.

If you are setting up inbound Web services, you must perform these three steps as prerequisites:

All exchanges require that you set up the transfer using the following forms:

These forms are optional for document exchanges regardless of transport:

  • Configure global defaults on the form. Global defaults configure adapters, actions, resource locks for batch processing, and schema validation, as well as the default encoding format for documents. See Configure global settings for document exchange.

  • Configure optional document transformations on the form. Optional document transformations include XSLT style sheet mapping and value substitutions. See Configure a pipeline.

  • Set up optional pre-defined value mapping that is available for certain documents on the form. See Configure endpoint action policies.

For adapter-based exchanges you also configure an adapter, a transport mechanism, a channel, and the batch jobs that process documents in the queues using the following steps:

  1. Perform any prerequisite steps for your transport mechanism.

  2. Configure an adapter using the form. Adapters are software components that translate the XML document into a format for a particular transport, for example, Message Queuing or file system. See Configure an adapter.

  3. Configure a channel using the form. Channels specify the direction for a particular transport in an adapter-based exchange. You also specify a transport mechanism that corresponds to the adapter on this form. See Configure a channel.

  4. To set up the batch jobs that run the services that manage inbound and out documents in the queues for adapter-based exchanges, click > > and select from the , or forms. See Start and stop the asynchronous Application Integration Framework (AIF) services.