Hi,
I need to create a workflow who manage XML messages in input and output with MQ Series (a MOM like MSMQ). Then, this workflow must listen new messages from a queue, send a request, and wait a reply message from queues... and manage 30000 processes with a good performance (several minutes).
How host this workflow In a windows service A COM+ server In IIS In several hosts Several windows services
Thank you for your help
PS: I know BizTalk, but my client doesn't want this product.
Host a workflow with MQSeries
Hot Topic
- Link Error occurs utilizing WDK sample asyncnotify
- CreateInstance failed
- user assignment and activity state
- Debug Workflow from Winform App
- LAN Driver problem
- GoTo Activity
- While loop activity
- HTTPS dependency in CardSpace
- How to host data access objects for high volume, distributed systems given current state of .NET?
- Can not debug project after installing framework 3.0 and extensions for VS2005
Windows Vista
- WPF and SqlServer
- Build error in Imapi2 sample
- How to Track StateMachine Workflow in Database?
- Waiting for completion of more than one activity in a state machine workflow
- Why WF?
- Problem with Delay activity in listener activity Sharepoint Workflow
- ASP.NET and Sequential Workflows
- Designer unable to load .xolm files
- where can we find the full functional WF design tool with code writing
- Persistence when exposed as a web service?
Host a workflow with MQSeries
mlanners
This solution will be not a stateless solution because I need remember some informations when an application reply me. And this reply may be occured several seconds or several minutes after the request. Then, a persistence service is very important for this project.
Didier
Corey C.
To a first approximation, the answer is not affected by the fact that you're using WF. After all, the workflow runtime is just another dll loaded into your app domain.
So I'd recommend that you think about it first as though WF were not involved. I'd guess from your description that you want a stateless solution that scales out 'share nothing' across a farm of processing servers.
Dave