Be the first to like this
BizTalk Mapping Patterns & an Introduction to WABS Maps, Maps or Transformations are one of the most common components in the integration processes. They act as essential translators in the decoupling between the different systems to connect.
In the last couple of month I have been writing a free eBook about “BizTalk Mapping Patterns and Best Practices” that will soon be released, and this will be a good opportunity for you to see what you can expect. In this session I will try to address and explain some common mapper problems, specifying best practices and some of the best ways to address common problems by choosing the right approach. For me there is no perfect solution to solve a particular mapping problem, and most of the times we can find several ways to solve it depending on the experience and knowledge that we have or technologies and tools that we like to use, but all of them have advantages and disadvantages. Not always the best solution is the best approach to address the problem, you must understanding the problem and the requirements, researching the available options and taking actions to achieve your goals sometimes base on:
•What’s the best approach to have performance? Is my message so big that I really need to worry about performance? Do I really need High performance?
•Can I easily maintain this map? It is easy to read and understand? What the estimated effort for debug, finding and fix problems?
•What the expertise levels required to create and maintain this map approach? What much time do I need to develop?
Finally I will try to make an introduction to the Windows Azure BizTalk Service maps, at the first glance the map editor seems to be the same that we used in BizTalk, but although the concept be the same this is a very different editor. And hopefully you will enhance your skills when using BizTalk Server and WABS Mapper editor
BizTalk Summit 2014, London March 03-04
Brought to you by BizTalk360
Clipping is a handy way to collect important slides you want to go back to later.