Harmony Microsoft Dynamics AX Agent Configuration¶

Introduction¶

A Microsoft Dynamics AX connection requires the use of a Harmony Windows Private Agent with a Jitterbit Microsoft Dynamics AX REST Connector. These two pieces of software must be downloaded, installed, and configured prior to the use and configuration of the Cloud Studio Microsoft Dynamics AX Connector.

Prerequisites¶

These are the prerequisites for the Jitterbit Microsoft Dynamics AX 4.0, 2009, and 2012 AX REST Connectors:

• A Windows Private Agent.

• The .Net framework 4.0 or above is required.

Installing and Configuring an Agent and Jitterbit AX REST Connector¶

Follow these steps to install and configure the agent and Jitterbit AX REST connector:

• Step 1: Install a Harmony Windows Private Agent

• Step 2: Install and configure a Jitterbit AX REST Connector

• Step 3: Test the Agent and Connector Windows Service Configuration

Step 1: Install a Harmony Windows Private Agent¶

Instructions on installing a Harmony Windows Private Agent are detailed on Installing a Harmony Windows Agent.

Once you have the Private Agent installed and it appears in the Harmony Management Console Agents page as Running, proceed to installing the appropriate Jitterbit AX REST connector.

Step 2: Install a Jitterbit AX REST Connector¶

Different versions of the Jitterbit Microsoft Dynamics AX REST Connector are available for download, depending on the version of Microsoft Dynamics AX you are connecting to. All Jitterbit AX REST connectors are available from the Jitterbit Harmony Downloads page and are listed under Connectors:

Choose the Jitterbit Microsoft Dynamics AX REST connector based on the Microsoft Dynamics AX version you are connecting to:

From the Downloads page, download and install the appropriate connector, following the instructions given by the installer. The installer must be run on the same server where the Windows Private Agent is installed and running.

If you have multiple Private Agents in an Agent Group, repeat these installation steps for each agent in the Agent Group.

After you have installed the appropriate Jitterbit Microsoft Dynamics AX REST Connector, ensure that the server where both the Microsoft Dynamics AX REST connector and the Windows Private Agent are installed can resolve the DNS name of the AX server. To do this, open a Command Prompt and run ping <DNS name of AX server>. If an IP address is returned, proceed to Step 3: Test the Agent and Connector Windows Service Configuration.

If an IP address is not returned, edit your driver host file (C:\Windows\System32\drivers\etc\hosts) and add an entry with the IP address of your AX server. This will enable the DNS name of the AX server to resolve.

Step 3: Test the Agent and Connector Windows Service Configuration¶

In the Windows OS Services console (services.msc), check that the Jitterbit Microsoft Dynamics (AX 4.0, AX 2009, or 2012) REST Connector Service is installed and running. If it is not running, start it and set it to automatic start mode.

Check http://localhost:8002/AX/help in a browser. This will show you the operations available in the connector service. If you do not see the list of operations, this usually indicates that the Windows service hosting the connector has not started.

Troubleshooting¶

To debug issues with a Jitterbit Microsoft Dynamics AX REST connector, set EnableWCFMessageTracing to true in the REST connector's configuration file. The configuration file for the Microsoft Dynamics AX 2012 REST connector can be found in this location:

C:\Program Files\Jitterbit\Jitterbit Dynamics AX 2012 Connector REST Service\Jitterbit.Connectors.Dynamics.AX2012.Host.exe.config