As I understand it , Biztalk will be build upon WWF one version after the comming 2006 version.
I suppose a migration path from BTS 2004 to BTS 2006 will be available.
I don't think there will be a migration from BTS 2004 to WWF : they are unrelated technologies.
I would probably go for Biztalk 2004 if I need all the features of BTS like reliable messaging , adapters, scaling out/in, survival of process restart etc...
Again just my 2cents.
I agree with Yves Lorphelin's post - Windows Workflow Foundation is an enabling technology thus acting as a platform for further development.
The relationship between BizTalk and Windows Workflow Foundation is becoming clearer: BizTalk could end up acting as a Windows Workflow Foundation host. The basic idea is that host applications add their own functionality to add value to Windows Workflow Foundation; as a result, BizTalk is likely to still be a product although its implementation could be quite different than it is today.
So the short answer is that you're safe with BizTalk 2004 and 2006. I suggest that you use Windows Workflow Foundation to add value to your BizTalk based-projects - not to replace them.
- We have some workflow features in our application, implemented with home-grown code.
- We are looking to enhance our workflow features now, probably before WWF or BizTalk 2006 are RTM (scheduled for H2 2006).
- Most of our workflow requirements are document centric "human workflow". We believe WWF meets most of our requirements. We also understand that "human workflow" is not BizTalk's strongest feature.
My delima is:
If I start with BlitzTalk 2004 'today' for human workflow senarios, will there migration path for those workflows into WWF after its RTM.
This might be a problem that you should talk to with your local Microsoft reprensentative. It would allow you to go a bit deeper on your requirement & delivery time in a more private fashion.
There is no migration planned from BizTalk Server human workflow services to Windows Workflow Foundation. The two are quite different technologies, see this article "Choosing the right workflow implementation with BizTalk Server 2004".
However if you go with BizTalk Server 2004 orchestration the upgrade experience to BizTalk Server 2006 is 1) stop services, 2) run setup, 3) start services. The version of BizTalk after 2006 is planned to be built on Windows Workflow Foundation and we also plan to have a migration tool from XLANG/S orchestrations to the Windows Workflow Foundation workflow model.
Office "12" will have document centric workflow capability built on Windows Workflow Foundation so maybe consider that also.