Today we will briefly go through the usage of Microsoft Dynamics CRM 2011 Online data in external applications. The most interesting business case there is the usage of Windows Azure cloud hosting for our application. Windows Azure has some differences comparing to common dedicated server environment. That is why it requires another approaches to applications development and integration.
So, lets say that we have a web site which hosts fast and beautiful Silverlight application. And we would like to show some data within the application. Lets also say that we are a small company who would like to use all benefits of Windows Azure hosting environment.
Scenario: direct access from Silverlight to Dynamics CRM 2011 Online
The standard approach to our case is to host an application as a Windows Azure web site. The web site will host a Silverlight application. The Silverlight application will access a MS CRM 2011 Online and will grab a data. There is the only one weakness in this plan: CRM Online didn’t publish cross domain policy files like crossdomain.xml and clientaccesspolicy.xml. There is no tools to somehow manage this or upload the files as resources. This does mean that you are not able to connect to CRM Online using Silverlight instead you host it within the CRM. But such scenario requires that all your visitors were registered as a CRM users what is not possible for internet-facing application. Lets work around this problem.
Scenario: access to CRM 2011 Online Organisation service from a web server
The approach with accessing CRM from a web server component requires some extra work. First, we need provide a WCF RIA service for the Silverlight application. This service will wrap a call of CRM Organisation service. Additionally it could be used to increase the security of the application and restrict an API access.
For that scenario it is required to have a Windows Identity Foundation installed on a server. As expected, there is no WIF installed in a cloud. So you need to add a reference on Microsoft.IdentityModel.dll (C:\Program Files\Reference Assemblies\Microsoft\Windows Identity Foundation\v3.5) in a project with parameter CopyLocal = true. The code for interaction with CRM uses proxy classes from SDK and entities classes generated by CrmSvcUtil.exe. Class DeviceIdManager also available in SDK samples (sdk\samplecode\cs\helpercode):
string userName = "<windows live>";
string password = "<live password>";
ClientCredentials credentials = new ClientCredentials();
credentials.UserName.UserName = userName;
credentials.UserName.Password = password;
Uri organizationUri = new Uri(@"https://techart.api.crm5.dynamics.com/XRMServices/2011/Organization.svc");
Uri homeRealmUri = null;
Uri issuerUri = new Uri(@"https://login.live.com/extSTS.srf");
string deviceName, devicePassword;
DeviceIdManager.PersistToFile = true;
ClientCredentials cred = DeviceIdManager.LoadDeviceCredentials(issuerUri);
deviceName = cred.UserName.UserName;
devicePassword = cred.UserName.Password;
DeviceIdManager.PersistToFile = false;
deviceName = "cvrmd6i7y6fozei5renofkmt";
devicePassword = "-r~-~pe`3ecWZ+ExW3Kb%F#Z";
ClientCredentials deviceCredentials = DeviceIdManager.LoadOrRegisterDevice(issuerUri, deviceName, devicePassword);
OrganizationServiceProxy proxy = new OrganizationServiceProxy(organizationUri, homeRealmUri, credentials, deviceCredentials);
Xrm.XrmServiceContext context = new Xrm.XrmServiceContext(proxy);
techart_growerapplication gapp = new techart_growerapplication();
gapp.techart_firstname = app.FirstName;
gapp.techart_FamilyName = app.LastName;
gapp.techart_SecondName = app.SecondName;
gapp.EmailAddress = app.Email;
The important notes for this code:
- The exact URI for issuer in your case can be found in WSDL for Organisation service under
or you can use WsdlTokenManger class demonstrated in SDK (sdk\samplecode\cs\wsdlbasedproxies\online).
- The call of EnableProxyTypes is mandatory. You will receive an exception without it:
The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http:
- Set the DeviceIdManager.PersistToFile = false and device name and password is mandatory in order to make it working on Windows Azure. Device ID will be registered in Windows Live. Windows Azure do not support storing the user or machine level files, that is why we should restrict the storing of the Device ID. As you can see, it is only required for release environment on Windows Azure.
So, this scenario will allows you to implement the required behaviour.
Scenario: using Windows Azure Service Bus and ACS to interact with Dynamics CRM 2011 Online
This scenario allows you to use all benefits of the Microsoft cloud platform. Dynamics CRM 2011 Online has an internal support for integration using Azure Service Bus. Commonly you can download a certificate from CRM and use it to maintain a trusted relationships with another application through Service Bus. Details regarding the configuration you can find in training materials by Microsoft.
So, this is in general it. The main issues will rise as always during the implementation of the solutions. But currently Azure provides spectacular tools which allows you to deliver a solution as quick as possible and do not worry about the hosting environment maintenance and support. Azure Service Bus could be expensive for small company, but it is a good tool for middle size organisations. I must admit that the current implementation of the Service Bus is far from enterprise level product and you should consider other available products such as MS BizTalk On-premises, Oracle Service Bus or Tibco EAI. But I expect that in two years it will become a real pearl for integration projects.CodeProject