Hello,
I'd like to start by mentioning that BizTalk can certainly do this,
but so can Windows Workflow. I'm going to paraphrase Darren Jefford
in his excellent book "Professional BizTalk Server 2006". He states
that Windows Workflow is a great tool for making applications (or
workflows) where as BizTalk is a great tool for integrating
applications. Basically workflow within an application is a good
candidate for WF and workflow between applications a good candidate
for BizTalk.
If your workflow does not integrate many applications and does not
need to be ultra scalable I might almost suggest a Sharepoint 2007
Windows Workflow using Visual Studio 2008. I've only been working
with it for a few months now, but it is really quite easy and will
even make task lists and all kinds of things. If you already have
sharepoint or want it (and remember you can use WSS 3 without
sharepoint server, so it's free) then it's a good platform.
You could also combine the two if your requirements are more complex,
which I've been doing lately.
How many concurrent workflow instances are you suspecting you will
have and how long will they last? This could help guide you a little
as well.
Kind Regards,
-Dan
|
