Just like its predecessor, once the source and the destination XML have been defined, the mappings can be created by drawing a line from one of the source fields to the desired destination field(s). Since drawing a large number of data mappings can easily become confusing, it also offers a tabbed interface, so the transformation can be grouped into sections of data mappings.
If the transformations you need require something more complex than simply mapping data from one place to another, BT includes a pre-defined library of .NET-powered functions to perform a wide variety of operations. Logical, mathematic, string operations, etc., can all be easily added to the the mix of data mappings to transform the XML into something useful.
If your transformations also require something that BizTalk's library of functions doesn't have, it also allows you to develop your own. BT allows you to enter
.NET code directly into the mappings. Thanks to its integration with Visual Studio, it can compile the code on-the-fly while generating the
XML transform file. Customized functions can be created through any of the .NET languages (Visual Basic, C++, C#, and J#), either by entering the code inline, or referencing it as an external assembly. If you'd rather do without all the .NET code, BT 2004 also allows you to write the function in XSLT for maximum flexibility in customization.
MapForce 2004
Once the source and the destination locations are defined, MapForce also provides a library of pre-installed functions
to aid in the creation of complex XML transformations. And like BizTalk 2004, if the list of functions doesn't contain
the operation you need, you can create your own custom functions.
However, unlike BT, the functions are not strictly based on .NET programming. MapForce instead offers the choice of XSLT, C++, C#, or Java to be the basis of your functions. While it doesn't boast the instant integration with .NET that BizTalk does, the fact that MapForce supports functions from both C# and Java allows it the flexibility to create XSLT that can work both inside and outside of the .NET framework.
Not all developers create applications for the .NET framework (or even Windows for that matter),
so being able to develop with portability in mind is always a plus.
One feature that I found extremely useful in MapForce 2004 was that it could easily specify multiple sources and destinations. I could take in data from multiple XML files or databases, and preview the XSLT code that would be generated for multiple possible transformations.
Granted, it can only generate the XSLT code for one destination at a time, but being able to preview the work for mutliple targets simultaneously can potientailly shave hours off of development time.
Functionality: Conclusions
BizTalk 2004's integration with Visual Studio gives it the power to add and compile
customized functions for you on-the-fly, and its compatibility inside of .NET applications
is virtually guaranteed. However, if .NET integration isn't your top priority, and you want to work with multiple possible sources/destinations within XSLT, MapForce is most definitely worth a shot.
- "Biztalk Mapper 2004 vs MapForce 2004, Page 1/3"
- "Biztalk Mapper 2004 vs MapForce 2004, Page 2/3"
- "Biztalk Mapper 2004 vs MapForce 2004, Page 3/3"
