CRM 2011 & database mirroring

In most scenarios where you implement CRM 2011 in Enterprise segment you would choose for database clustering. The advantage is that your setup is easy, at least I think so :) You have virtual name for your SQL server no need for extra CRM configuration.

Another alternative is to choose for database mirroring, also supported scenario. Please keep in mind that besides configuration of SQL server is more complex. You also need to make changes to CRM, which can be forgotten easily.

For example you need to change some settings in the registry on the server where the web application is installed:

1) Locate:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM\
2) Change: configdb

Data Source=MSCRM_Primary\SQL1;Failover Partner=MSCRM_Mirror\SQL2;Initial Catalog= MSCRM_CONFIG;Integrated Security=SSPI

You can image when you do node switch and forget this entry your CRM application will crash. More details at: http://technet.microsoft.com/en-gb/library/hh699791.aspx.

More background about database mirroring:
http://www.c-sharpcorner.com/uploadfile/nipuntomar/sql-server-database-mirroring-part-1/

PS If you wondering about the image, read this article about Droste Effect  :-)

Understanding integration concepts

In my experience as Dynamics CRM consultant I am also involved in several integration projects. The requirements should be business driven, but it still happens that requirements for integration are defined by the IT/support organization.

In some cases due to lack of knowledge people tend to define or choose requirements within their comfort zone. Of course this is not surprising because it is for them known area and they basically keep doing their work without being confronted with new technology or new software.

The downside is that the integration design gets more complex as it should be. I prefer to design integration with according to the  'loosey coupled' principle, which basically means that source(s) and target(s) have no direct links.

In this scenario you would have for example a generic account template. A system that want to deliver account information used the template (in xml format) and the integration process moves it to the desired target system. Very import in this scenario that the templates are defined and changes have major impact, so you would need to take time to define a good generic template. Of course in case you use Scribe as integration platform you need to define a xdr or xsd file. In this file you define all fields, required, data types etc.

In the integration scenario where you exchange xml files you would most likely use MSMQ as reliable and proven technology. In my next post I will explain more about this scenario using Scribe Insight.

So, explore new possibilities by stepping out your comfort zone it could make your life less complex....

Latest musing now on MSDynamicsworld

Last month, I finally got some time to write new musing. This time about the topic of documentation and handing over your CRM application into support.

It still amazes me that so little attention is spend on value of documentation, especially in enterprise segment. This is a key requirement when you hand over your xRM solutions to the support organization.

But read my musing at msdynamicsworld... yes, click here :)

Happy 2013!

Happy and friendly 2013!

A blend of integration solutions

Finally, some time to update my blog. I have been mostly working on integration and migration projects to CRM2011 the last couple of months.

My integration designs are for at least one project a mixture of several technics, mostly due to requirements from the IT department and you might say this is also limiting factor.

Nevertheless, it is interesting to just different approach, basically I use four kinds of approaches:

• Standard and custom web service
• Standard and custom database views
• Integration based on MSMQ with of course Scribe Insight
• .NET application

The overal design is "loosely coupled" and between CRM 2011 and legacy systems we have integration database in place. For integration that is synchronous we use of course webservice. For integrations that need to just use data, we use database views and results are stored in memory on the legacy application.

For extracting data from CRM 2011 we use mostly plugins and for a-synchronous processes we use MSMQ.

So basically a nice blend of several technics some technics, which make a integration interesting :)

CRM 2011 Rollup 10 available

Finally some time to update my blog and what a surprise. We have new update rollup available too. You can find the details about the latest version at kb article: 2710577 and  download can be found  here.

If you look closely they also offer automatic translation, my kb was presented in Dutch but with the link "click here for automatic translation" It was translated by http://www.microsofttranslator.com, kinda funny because with language code in the kb-article url the article is already available, so why translate it.

 Further, I have been busy with some coding and enhancing the (kb) article entity, which needed some 'creative' steps, but more in next post.

Happy updating :)

Simply jump for (Scribe) AX-CRM integration

At the end of the month Scribe is releasing, yes it is still  May 31st here, the new integration between CRM 2011 and AX 2012.

Most interesting change from technical point of view that for the integration the web services adapter is used and primary keys are stored in source and target system.

The web service adapter is one of the very interesting and useful integration options of Scribe Insight. It gives you many opportunities to integrate with all kind of other application.

Of course we like to have integration 'out of the box' and we know that could be hard to achieve, I won't mention Microsoft Connectors here ;-)

Luckily, Jumpstart makes it easy to set up your basic integration(s). In a nutshell the solutions comes with  the components for CRM 2011, AX 2012 and Scribe Insight to setup your integration. Next you have to do a little configuration and you up and running.

By the way you need the new version 7.5.1, which is also released today and offers for example enhanced web service adapter functionality. Also supporting MS SQL 2012.

AX-CRM Jumpstart

The principle for integration is similar to other integration you can achieve with Scribe Insight. The core is Microsoft Message Queue. The changes from source system are published to the queue processed by Scribe Insight and send to your target system and vice versa.

Of course, every integration is custom and sometimes you lucky you get away with standard integration. Nevertheless this is a great step to get your basic integration up and running and take it beyond!

Happy Jumping.... you can start NOW!