The final release of the Microsoft Enterprise Service Bus (ESB) Guidance for BizTalk Server 2006 R2 is now on MSDN. The Microsoft ESB Guidance provides architectural guidance, patterns, practices, frameworks, reusable components and samples for BizTalk Server 2006 R2 to simplify the development of an Enterprise Service Bus (ESB) on the Microsoft platform and to allow Microsoft customers to extend their own messaging and integration solutions.
Some of the core capabilities provided by the ESB Guidance include:
The BizTalk Server 2006 R2 Extensions for Windows Workflow Foundation SDK has just been released. It allows the ability to use WF modeling and host WF-based workflows in BizTalk Server.
The release of this SDK will hopefully answer the many questions developers have had with regards to when to use BizTalk Server vs Windows Workflow Foundation for a process related application and will hopefully showcase the "better together" story in that both technologies are quite complimentary. The SDK also ships with a sample of how to build a wrapper BizTalk orchestration for a WF-based workflow that can be deployed to BizTalk Server. This presents a powerful solution as it provides the flexibility of WF coupled with the robust services provided by BizTalk Server, like adapters, business activity monitoring and tracking infrastructure, deployment management, scalability, etc.
This SDK Sample provides a good alternative to having to face the sometimes difficult choice between BizTalk Server or WF by directly allowing you to choose both.
So download today and let us know what you think!
We've officially launched a new website dedicated to providing invaluable information around building Services Oriented Architecture (SOA) and Business Process Management (BPM) solutions using the Microsoft platform. As a part of this site, we've released our latest roadmap and product strategy around the next generation of Microsoft SOA-based technologies, codenamed "Oslo", to included updated messaging and workflow technologies in BizTalk Server and other products starting in 2009.
The "Olso" vision will leverage the next version of BizTalk Server as it's primary delivery vehicle for delivering a superior SOA infrastructure, but that's not all. "Olso" will also feature updates to the Visual Studio development environment and the System Center line of systems management products as well as provide the appropriate infrastructure support to support business-to-business composite applications.
This is going to be an exciting ride in the world of SOA, and Microsoft will be right there in the mix!
We've made some updates to the BizTalk Server Roadmap that will hopefully shed some light on what the plans are for the product with the pending R2 release as well as future versions of the product. BizTalk Server 2006 R2 will feature a number of updates over the initial 2006 release including rich integration with Windows Communication Foundation and Windows Workflow Foundation through the WCF Adapter SDK and new Business Activity Monitoring (BAM) interceptors for WCF and WF which will enable you to leverage BAM functionality in non-BizTalk applications, updated support for the 2007 Office System (which includes an update adapter for SharePoint Server), and comprehensive RFID support.
In addition to all the new capabilities introduced in BizTalk Server 2006 R2, the roadmap also provides a "sneak peak" in to the future strategy of BizTalk Server and the investments that are being made. Head on over to the roadmap and check it out.
Yeah, I know it's been AGES since my last blog post. I'm not going to even begin making apologies or excuses. I will say to those who've followed my blog, that I am going to start ramping up the frequency of my blogging, as I have a lot to talk about. Upon joining Microsoft last January, I've not had much time to do a lot of things I did before I joined the collective. Needless to say, however, that since joining Microsoft, I've gotten to see (or at least hear) about a number of new initiatives coming out of Redmond that's geared at making developer's lives a lot better.
For those of you who used to follow my blog on DotNetJunkies.com, you'll probably remember I had a series of posts on my design/development process around a custom XML-driven workflow engine I was working on (BTW, I'll be posting an archive of those posts on my new blog here). Well, had I known then what I know now, I'd have definitely tried to get onboard our TAP (Technology Adoption Program) and gotten my customer involved with exploring Windows Workflow Foundation (formerly known as Windows Workflow Services and Windows Orchestration Engine (WinOE)) as well as pushed Microsoft in trying to support our current platform with a release of WF that'll work with v1.1 of the .NET Framework!
Windows Workflow Foundation, in a nutshell, is our new framework for building workflow-enabled applications. It consists of a programming model, a full-blown workflow engine, and developer tools for building custom workflow solutions. WF will sit as another namespace within our WinFX stack (System.Workflow) and will provide the necessary tools for building compelling workflow solutions for the Windows platform. Working here at the Microsoft Technology Center, one of my focuses is around connected systems and business process automation, alongside portals/collaboration of course [:)],and I've engaged with a number of customers who are searching for a solution to address their need for introducing workflow into their applications without having to resort to BizTalk Server or going with third-party workflow solutions. With WF, we now have technology that we can position as an alternative solution that delivers rich functionality out-of-the-box for introducing workflow within their enterprise applications.
Over the course of my next several posts, I drill into Windows Workflow Foundation and discuss how you can build some value adding solutions with the technology. As my own personal case study that'll fuel the posts, I'll use the custom engine I wrote a year ago and blogged about during my time on DotNetJunkies and completely rearchitect it to work with WF as well as Windows Communication Foundation (formely known as "Indigo").
But before I go hog wild about WF, let me first set some groundwork around the technology and basically tell you what it is NOT
I've been working with this technology for the past several months now and I have to admit that this is one of the coolest things I've seen. I strongly recommend that you go and download the whitepapers and the bits and get started in building compelling workflow solutions!