What are the differences in the Boomi Connectors for MS Dynamics / Great Plains?

Document created by mike_aronson Employee on Jan 20, 2014Last modified by mike_aronson Employee on May 17, 2017
Version 3Show Document
  • View in full screen mode
  • Boomi has different Connectors for the different MS Dynamics Products:

 

Great Plains Connector

 

Microsoft Dynamics GP Connector

 

Microsoft Dynamics CRM Connector

 

Microsoft Dynamics AX Connector

 

This article covers the differences between the Great Plains Connector and the Microsoft Dynamics GP Connector only

  • Prerequisites:

    • This connector requires a Windows atom (will not work with a Linux atom)

    • Great Plains, eConnect, MS SQL Server DB and a Local Atom
    • See section at link above for more details

    • SFDC Article # 1222 "Great Plains Integration" with more Pre-requisites

  • The Great Plains Connector for 9.x and 10.x connects to eConnect using the Microsoft COM+ APIs and requires IKVM.NET which brokers between the atom’s JVM and .NET

  • Atom installation can be on same or different server than Great Plains, eConnect and SQL Server;  the Boomi GP connector installation is compatible with 64-bit installs

    • Installing atom on same server is typically easier to configure

    • Some 32-bit Great Plains 9.x or 10.x installations may cause a “No such Object in table” error - this may require an interim connector (bootleg) that Boomi Support can provide if needed)
       

  • Microsoft Dynamics GP Connector

  • Only works with Microsoft Dynamics GP 2010 and 2013 (note: 2010 is different than GP 10.x)

  • Link to Boomi help: http://help.boomi.com/atomsphere/GUID-A14D7B34-4982-4054-B621-D9B193E22E02.html

  • Prerequisites:

  • Microsoft Dynamics GP 2010 and 2013 are able to communicate through an API with eConnect running as a Windows Service (more advanced than the COM+ API in previous versions)

  • Atom installation can be on same or different server than Great Plains, eConnect and SQL Server

    • Installing atom on same server is typically easier to configure; HTTP Endpoint would be localhost

    • Installing atom on a different server would require the hostname/port as the HTTP endpoint and firewall would need to be opened by client

2 people found this helpful

Attachments

    Outcomes