Contact Us 1-800-596-4880
  1. Homepage
  2. Microsoft Dynamics AX 2012 Connector (3.0)

  3. Upgrading and Migrating Microsoft Dynamics AX 2012 Connector

All Connectors

Upgrading and Migrating Microsoft Dynamics AX 2012 Connector to 3.x

Upgrade Anypoint Connector for Microsoft Dynamics AX 2012 (Microsoft Dynamics AX 2012 Connector) from version 2.x to version 3.x.

Supported Upgrade Paths

From Version To Version

2.x

3.x

Changes in This Release

3.0

  • This connector is now compatible with Java 17 only. Java 8 and Java 11 are no longer supported.

  • This connector now requires Mule runtime 4.9.0 or later.

  • Metadata, query, and document SOAP calls now go through the Mule SOAP engine, instead of a direct Apache CXF 3 client. Call context, the routing header (sent once), basic authentication, gzip, and certificate-name checking now use the Mule HTTP dispatcher. Operation names and the microsoft-dynamics-ax configuration prefix are unchanged.

    For more information, see Gateway Username Password Connection Type, Query Table, Static Query, and Invoke Document Service Operation.

  • Generated client stubs now use Jakarta XML APIs, instead of Java EE XML APIs.

  • Imported WSDL and schema documents are now parsed with the same XXE-hardened XML builder as the root document.

  • When a host cannot be resolved, the connection test still appends Unknown host: and the host from the exception. If the failure is an unresolved address with no host string, the message uses the Aos Server Name value. This release doesn’t add error types.

  • These libraries are upgraded to address reported security vulnerabilities:

    • Gson is upgraded to version 2.14.0.

    • ASM is upgraded to version 9.11.1.

    • The Jetty HTTP, I/O, security, server, session, utility, XML, EE web application, EE 10 servlet, and EE 10 web application libraries are upgraded to version 12.1.14.

    • The Apache Commons Lang library is upgraded to version 3.21.0.

    • The Jakarta XML Binding API is upgraded to version 4.0.5.

    • The Jakarta XML Web Services API is upgraded to version 4.0.3.

    • The Jakarta JWS API is upgraded to version 3.0.0.

    • The Jakarta Annotation API is upgraded to version 2.1.1.

    • The JAXB runtime is upgraded to version 4.0.9.

Requirements

Ensure your system meets the following compatibility requirements before you perform the upgrade:

Application/Service Version

Mule runtime

4.9.0 and later

Java

17

Microsoft Dynamics AX

2012

Upgrade Prerequisites

Before you perform the upgrade, you must:

  1. Create a backup of your files, data, and configuration in case you need to restore to the previous version.

  2. Ensure that your environment meets the version 3.x requirements, including Java 17 and Mule runtime 4.9.0 or later.

  3. Re-verify applications that depend on a direct Apache CXF 3 client or Java EE XML APIs.

  4. Install Microsoft Dynamics AX 2012 Connector 3.x to replace the connector operations that were previously included in version 2.x.

Upgrade Steps

Follow these steps to perform the upgrade from Microsoft Dynamics AX 2012 Connector 2.x to Microsoft Dynamics AX 2012 Connector 3.x:

  1. In Anypoint Studio, create a Mule project.

  2. In the Mule Palette view, click Search in Exchange.

  3. In the Add Dependencies to Project window, enter Microsoft Dynamics AX in the search field.

  4. In the Available modules section, select Microsoft Dynamics AX 2012 Connector and click Add.

  5. Click Finish.

  6. Verify that the mule-microsoft-dynamics-ax-connector dependency version is 3.x.x in the pom.xml file, where x.x is the minor release and patch version number. For example, if you are upgrading to version 3.0, the dependency version in the pom.xml file should be 3.0.0.

Studio upgrades the connector automatically.

Verify the Upgrade

After you install the latest version of the connector, follow these steps to verify the upgrade:

  1. In Studio, verify that there are no errors in the Problems or Console views.

  2. Check the project pom.xml file and verify that there are no problems.

  3. Test the connection and verify that the operations work.

Troubleshooting

If there are problems with caching the parameters and caching the metadata, try restarting Studio.

Revert the Upgrade

If it is necessary to revert to the previous version of Microsoft Dynamics AX 2012 Connector, change the mule-microsoft-dynamics-ax-connector dependency version in the project’s pom.xml file to 2.0.7.

Rollback is a connector downgrade. There is no data migration.

You must update the project’s pom.xml file in Anypoint Studio.

See Also

Back to top