How to create Dynamic send port for MS CRM 3.0/4.0 in BizTalk 2006?

Question

HI ,

I want to create a dynamic send port for MS CRM 3.0/4.0 adapter. but i didn't get how to create it? Also i didn't get any methods to set user name and password required to access CRM.

CRM URL is : http://localhost:5555

User name: Administrator

Password: password

Orgname: MicrosoftCRM

I installed MS CRM Adapter[Both for 3.0/4.0 common and also separate adapter for CRM 4.0].

Thanks in advance.

Answer 1

There is a lot to configure from BizTalk end.

I suggest having a look at this blog as it introduces the MS CRM Webservices including their FetchXML grammer and BizTalk adapter.

https://blogs.msdn.com/brajens/archive/2007/05/27/using-microsoft-biztalk-dynamics-crm-adapter-part-1.aspx

http://blogs.msdn.com/brajens/archive/2007/05/30/using-microsoft-biztalk-dynamics-crm-adapter-part-2.aspx

Also here are the links to the CRM SDK Webservices

http://msdn.microsoft.com/en-gb/library/aa682250.aspx

And the Developing with them http://msdn.microsoft.com/en-gb/library/aa681429.aspx

And finally and invaluable tool for working with MS CRM Webservices is FetchXML Builder

**

1. You should also read the installation guide for MS CRM 4 as there is the process for setting up the BizTalk adapter with the Current and Different CRM Accounts too.

**

http://www.microsoft.com/downloads/details.aspx?FamilyID=1ceb5e01-de9f-48c0-8ce2-51633ebf4714&displaylang=en

Answer 2

HI i got new errors for MS CRM Dynamic Solicite-response send port

1.A message sent to adapter "Microsoft Dynamics CRM" on send port "CreateContactOrch_1.0.0.0_CreateContactOrch.Orchestration_1_Dynamic_CRM_Solicit_Response_Port_8de755fbdbd4eff7" with URI "MicrosoftDynamicsCRM://http://10.1.3.140:5555" is suspended. Error details: The file '/metadataservice.asmx' does not exist. MessageId: {79866086-E694-4965-A6A4-83AD3D83D6F4} InstanceID: {95B7B876-6710-4230-851D-8ABD6DA10795}

2.A message sent to adapter "Microsoft Dynamics CRM" on send port "CreateContactOrch_1.0.0.0_CreateContactOrch.Orchestration_1_Dynamic_CRM_Solicit_Response_Port_8de755fbdbd4eff7" with URI "MicrosoftDynamicsCRM://10.1.3.140:5555" is suspended. Error details: The file '/metadataservice.asmx' does not exist. MessageId: {C34375C3-56D5-465F-96D1-3D72C34B7F67} InstanceID: {1B6AD9FE-9984-4F55-8852-60B095DD9F3F}

Answer 3

WORKING SOLUTION

This is what you would need to do...

Add the Dynamics CRM Property Schema 'PropertySchema.xsd'. Locate this schema in the Microsoft CRM Dynamics BizTalk Adapter installation folder

C:\Program Files\[CRM Adapter installation folder]\Schemas

Set the following properties in the orchestration

// NOTE: Use the complete MS CRM 4.0 Web Service URL and not the short form
    CrmQueryRequest(PropertySchema.ServerUrl)  
        = "http://server_name/MSCRMServices/2007/CrmService.asmx";
    CrmQueryRequest(PropertySchema.UserName) = @"domain-name\user-name";
    CrmQueryRequest(PropertySchema.Password) = @"p@ssword";

    CRMQueryPort(Microsoft.XLANGs.BaseTypes.Address)="http://server_name/MSCRMServices/2007/CrmService.asmx";
    // The name of the adapter listed in the BizTalk administration console
    CRMQueryPort(Microsoft.XLANGs.BaseTypes.TransportType) = "Microsoft Dynamics CRM 4.0";

For more information about Dynamic ports, please go through...

My Code Project Article

Answer 4

Unfortunatley I don't have any CRM-specific experience, or a CRM system I can test this with, but I'll try to help as much as I can "offline".

Starting with the dyamic send requirement - I've looked at the setup of the adapter starting at the registry entries (HKEY_CLASSES_ROOT\CLSID{D38D5DCC-2B30-43b9-9C69-3BBFD0926986}) and I found the registered alias for this adapter - "MicrosoftDynamicsCRM://"

Based on that, when you set the url for the dynamic port in your process, have you tried using this alias as a prefix to the url you need?

BizTalk uses the alias to decide which adapter to use for the dynamic send port.

As for the username/password - looking at the installation folder for the adpater I can see there's a schemas folder and in it a propertySchema.xsd - this one contains context properties which I assume are used to control the adpater's behaviour at runtime (as this is almost always the case) - the schema contains properties for username and password - I would try to set those on the outgoing message; they are likely to to be used by the adapter.

BTW - the third property is "serverUrl" - you might want to try setting this to override any url configured for a static port as a way of performing a "dynamic send", although if you can get the dynamic send port to work, and you should be able to, I would think that's the better way

Important note - at least on my machine the property schema was not deployed as part of the server installation, so you might need to deploy it manually (and reference it from your project)