简体   繁体   English

BizTalk CRM Dynamics 4到Dynamics 2011

[英]BizTalk CRM Dynamics 4 to Dynamics 2011

My client is doing an upgrade from CRM Dynamics 4 to 2011 and it uses BizTalk 2009 as its ESB, they are currently using the 'Microsoft BizTalk Server Adapter for Microsoft Dynamics CRM 4.0' for the Integration, my question is does anyone know what breaking changes are involved from a BizTalk point of view when this upgrade takes places? 我的客户正在进行从CRM Dynamics 4到2011的升级,它使用BizTalk 2009作为其ESB,他们目前正在使用“用于Microsoft Dynamics CRM 4.0的Microsoft BizTalk Server Adapter”进行集成,我的问题是是否有人知道哪些重大更改从BizTalk的角度来看,何时进行升级?

Am I looking at a whole new set of contracts in CRM 11 eg WCF meaning code changes, mappings, schemas and moving away from the Adapter (4.) to pure WCF transport communication? 我是否正在查看CRM 11中的一组全新合同,例如WCF,这意味着代码更改,映射,模式以及从适配器(4.)转向纯WCF传输通信?

At this moment in time I'm trying to gauge the complexity and migration levels for one service... 目前,我正在尝试评估一项服务的复杂性和迁移级别...

Cheers 干杯

I have some first hand experience integrating BizTalk with CRM Online 2011. 我有将BizTalk与CRM Online 2011集成的第一手经验。

The major difference is the change from the pre-defined CRM types, allowing compile-time type safety, to an un-typed Wcf interface. 主要区别是从允许编译时类型安全的预定义CRM类型更改为无类型的Wcf接口。 A couple of (ugly) solutions to this problem have been documented around the web, but this blog post by Richard Seroter defines a BizTalk-only solution. Web上已记录了针对此问题的几种(难看的)解决方案,但是Richard Seroter的这篇博客文章定义了仅BizTalk的解决方案。

We used a third-party supplied adapter , developed by Roedl in Germany. 我们使用了由德国Roedl开发的第三方提供的适配器 This uses the Wcf Adapter Framework, in a similar manner to the WCF-SQL adapter, to provide a set of compile-time strong-typed schemas. 它以与WCF-SQL适配器类似的方式使用Wcf适配器框架来提供一组编译时强类型模式。 This made it simple to map to and from the CRM types to our legacy system data types. 这使得在CRM类型与旧系统数据类型之间来回映射变得很容易。

One disclaimer, we found that performance was "sufficient", without being outstanding. 一个免责声明是,我们发现性能是“足够的”,没有出色的表现。 If you need to move a LOT of data back and forth, consider using the bespoke solution, but if lower development cost is your prime motivation, it is worth considering. 如果您需要移动数据的很多来回,可以考虑使用定制的解决方案,但如果降低开发成本是你的主要动机,这是值得考虑的。

The scope of this project as described will be huge especially considering the limitations of the BizTalk Server Adapter. 所描述的该项目的范围将非常巨大,尤其是考虑到BizTalk Server Adapter的限制。 Have they considered using Scribe? 他们是否考虑过使用抄写员? You might want to do a simple proof of concept project for them with the free evaluation version. 您可能想使用免费评估版为他们做一个简单的概念验证项目。 Scribe downloads 抄写员下载

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM