NOTE: Microsoft has removed the Instance Adapter.
The Microsoft Dynamics CRM 2011 Instance Adapter is an adapter that was written for the Connector for Microsoft Dynamics that allows for the synchronization of data between two 2011 CRM organizations. The CRM Instance Adapter allows for communication between two endpoints that exist on any authentication/hosting environment (on-premise, online and IFD) within one adapter. Previously it was required to utilize two adapters, as is the case when synchronizing data between two dynamics products like GP and CRM.
The Connector for Microsoft Dynamics must be installed on a machine that has access to both CRM endpoints you wish to communicate with and have access to a database server where it may deploy its configuration database. Be aware that the name of the configuration database is hardcoded into the installation of the connector and that installing a second instance while utilizing the same database server will overwrite the configuration database.
After the Connector has been installed, you can now add the CRM Instance Adapter.
My installation path: C:Program Files (x86)Microsoft DynamicsMicrosoft Dynamics Adapter
Upon opening the file you should see the following:
Inside the Adapters folder, you should notice a folder called Microsoft.Dynamics.Integration.Adapters.DynamicCrm:
Copy it into the Adapters folder in your Connector folder. My directory looks like the following:
My directory looks like the following:
Let’s explore the folder structure of the adapter a little. If you navigate to the DynamicCrm Adapter folder that we copied in the first step (C:Program Files (x86)Microsoft DynamicsMicrosoft Dynamics AdapterAdaptersMicrosoft.Dynamics.Integration.Adapters.DynamicCrm), you should see something like the following:
The adapter itself is stored in the Microsoft.Dynamics.Integration.Adapters.DynamicCrm assembly, while the remaining assembly is a reference utilized by the adapter. The ObjectConfig folder is where configuration files for the entities of your two CRM endpoints will be stored. After configuring the adapter, if you navigate into that folder, you’ll notice something:
The ObjectConfig folder contains a DynamicCRMAdapterSource and a DynamicCRMAdapterDestination folder that mirror the two parts of the DynamicCRM adapter. This split allows you to utilize the same CRM endpoint as both a Source and Destination in your Connector integrations and for flexibility in the configuration of each. For instance, if you wanted to modify the configuration files for an organization that is utilized as a source endpoint, you would not have to worry about those changes affecting a different integration where the organization is also utilized as a destination endpoint.
We’ll look further into the configuration file folders after we’ve had a chance to configure the adapter and run the configuration utility. Take a look at the next blog in our series which deals with configuring the adapter.