Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Throttling
- This topic has 3 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
June 26, 2008 at 5:10 PM #20006
Hello All
I have the follwoing scenario:
Phase 1:
A client’s business process createws around 400 XML files per day.
The client places these files into our FTP directory.
My BTS 04 process picks up the files and places them into another directory.
So we have a directory inside our domain with 400 files waiting to be processed.Phase 2:
At 7am I have another Biztalk 04 process that picks up each file and lauches a series of orchestrations that call other orchestrations and so on until the file is processed and an email is sent out.The problem is that at 7am 400 orchestrations will start and crash my system.
I need a way to stagger / throttle the system so that it starts – say 10 – at a time.Any ideas?
-
June 27, 2008 at 7:44 AM #20011
have you checked the last two issues of Biztalk Hot Rod magazine? Scott Colestock speaks to throttling in those two issues. I am not sure if all of it applies only to 2006, but it might give you some ideas.
Also, check out Richard Seroter’s blog post found at…
http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/
It is an implementation of the pattern that Scott Colestock refers to in his articles.
Unfortunately there is no “switch” that you can flip that would easily say “Only allow N instances of this orchestration to be active or dehydrated at any one time”
-
June 27, 2008 at 10:39 AM #20012
You should be fine using the BizTalk Singleton orchestration design shown there in the picture (just remove the last delay node – that exists to prove a point, not show a good design). If you want a good reference, read the MS white paper referenced on that blog. Basically, you want to receive the first message (file), and then loop. The problems referenced in the previously mentioned blog shouldn’t be your concern since you mentioned you only get new files once a day. Hope this helps!
-
-
June 29, 2008 at 4:32 PM #20016
Thanks for those responses but I guess I should have included something else. I have no control over the orchestration that runs at 7am. It is out of my hands. Which is why I was hoping that I could throttle it in a setting somewhere. If I were to use a singletone I would have to redesign the orchestration and I cannot do that.
Here is a response from a friend of mine ( here is his blog page by the way … http://connectedthoughts.wordpress.com I highly recommend it 🙂 )
****************************************************************************************
At least in BT 2006 you can create a host and host instance dedicated to the solution then modify the value for the AgentThreadPoolSize registry entry to limit the number of running orchestrations for that host. Not sure if this exists in 2004.
****************************************************************************************That is the kind of thing I was hoping to do. I haven’t checked it out yet though.
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.