BizTalk – another XML thingy
Lately, I was wondering about BizTalk and how far it will fly. If you have wondered yourself - you might want to read this link above:
BizTalk Server 2004: Ten things you should know
http://techrepublic.com.com/5100-7343_11-5795155.html?tag=crm
10. Your time cost will be enormous
If there ever in the history of Microsoft was a product that was hyped through the roof and then thrown upon the sea, it's BizTalk. Originally a Microsoft acquisition that is now well-integrated into Microsoft's family and lovingly nurtured by its caretakers, BizTalk is powerful, well-conceived, and at this point married to the rest of the MS family\u2014but at the expense of correct and thorough documentation. To say that useful BizTalk how-to and real-world labs are scarce is howling understatement. Buy into BizTalk and you're more or less on your own, bringing it around to your particular applications and environment.
In short, prepare for endless hours of blogging, followed by endless hours of trial-and-error. You'll get plenty of frustrating hints from the BizTalk Server Administration event log, vague exception messages, and precious little real debugging assistance from the Health and Activity Tracking utility. The upside is that once you've learned the quirks and fixes and tricks, you'll feel incredibly empowered. But, oh, what a learning curve! Don't underestimate it.
…
Ouch! Time to wake up and smell roses ... BizTalk was doomed from the begining IMHO. XML is good at presenting your hierarchical data and that's about it. For anything else you want to do with it - it's likely a bad idea and there is surely a better way to solve your problem without XML. You may try XML anyway, but you will be sorry in the end.
BizTalk Server 2004: Ten things you should know
http://techrepublic.com.com/5100-7343_11-5795155.html?tag=crm
10. Your time cost will be enormous
If there ever in the history of Microsoft was a product that was hyped through the roof and then thrown upon the sea, it's BizTalk. Originally a Microsoft acquisition that is now well-integrated into Microsoft's family and lovingly nurtured by its caretakers, BizTalk is powerful, well-conceived, and at this point married to the rest of the MS family\u2014but at the expense of correct and thorough documentation. To say that useful BizTalk how-to and real-world labs are scarce is howling understatement. Buy into BizTalk and you're more or less on your own, bringing it around to your particular applications and environment.
In short, prepare for endless hours of blogging, followed by endless hours of trial-and-error. You'll get plenty of frustrating hints from the BizTalk Server Administration event log, vague exception messages, and precious little real debugging assistance from the Health and Activity Tracking utility. The upside is that once you've learned the quirks and fixes and tricks, you'll feel incredibly empowered. But, oh, what a learning curve! Don't underestimate it.
…
Ouch! Time to wake up and smell roses ... BizTalk was doomed from the begining IMHO. XML is good at presenting your hierarchical data and that's about it. For anything else you want to do with it - it's likely a bad idea and there is surely a better way to solve your problem without XML. You may try XML anyway, but you will be sorry in the end.
posted by Zaphod at
2:04 PM
0 Comments:
Post a Comment
<< Home