Share via


Configure settings for Async Client

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Applies To: Microsoft Dynamics AX 2012 R3

The Async Client Configuration Tool can be used to configure an instance of Commerce Data Exchange: Async Client. This tool lets you test connections and specify whether to use streaming to transfer data. The configuration data is stored in the application configuration file.

The Async Client Configuration Tool is installed together with Async Client.

Note

You can configure the download and upload intervals for Async Client in Microsoft Dynamics AX. For more information, see Set up a profile for Async Server.

Test connections for Async Client

Use the Async Client Configuration Tool to test connections between Async Client and other components.

  1. Start the Async Client Configuration Tool. By default, the executable file is located at C:\Program Files\Microsoft Dynamics AX\60\CDX\Async Client\<DatabaseName>_Package. Double-click the AsyncClientConfigurationUtility.exe file.

  2. Test connections to other components, as shown in the following table.

    Async Client connection

    How to verify the connection

    Commerce Data Exchange: Async Server

    On the Async Server connection tab, in the Authentication information section, click Test connection.

    Channel message database

    On the Channel configuration tab, in the Channel message database section, click Test connection.

    Channel database

    On the Channel configuration tab, in the Channel database section, click Test connection.

Configure settings for Async Client

  1. Start the Async Client Configuration Tool. By default, the executable file is located at C:\Program Files\Microsoft Dynamics AX\60\CDX\Async Client\<DatabaseName>_Package. Double-click the AsyncClientConfigurationUtility.exe file.

  2. On the Async Server connection tab, verify or modify the information.

    The Async Server connection section contains information about how Async Client communicates with Async Server. The following fields are available:

    • Server name – The name of the server that hosts Async Server.

    • Application name – The name of the web application for Async Server.

    • Https port number – The port number that Async Server uses for secure HTTP communication.

    • NetTcp port number – The port number that Async Server uses for Net.TCP communication. Specify a Net.TCP port if you select the Use streaming option.

      By default, Async Client uses the WS-ReliableMessaging protocol. Reliable messaging helps guarantee that the data is transferred successfully. However, the confirmation actions between the source and the destination can cause data transfers to be slower. For better throughput, you can use streaming instead. Streaming is ideal for initial high-speed data synchronization or for ongoing synchronization of large amounts of data. If you have a reliable network and high data volume, we recommend that you stream data.

    The Authentication information section contains the identifier for the channel database that Async Client connects to. This section also contains the credentials that are used to authenticate Async Client with Async Server. These values are specified in the Channel database form. For more information, see Set up a channel database profile.

    Click Test connection to verify that the connection to Async Server is configured correctly.

  3. On the Channel configuration tab, verify or modify the information.

    • The Channel message database section specifies the server and database name for the channel message database. Click Test connection to verify that the connection to the channel message database is configured correctly.

    • The Channel database section specifies the server and database name for the channel database. Click Test connection to verify that the connection to the channel database is configured correctly.