| Yossi Dahan 2004-07-28, 2:55 am |
| There is no simple way in BTS 2004, as it does not support prioritizing
orchestrations.
There have been posts on how to implement an orchestration that runs only
once at a time, mainly keeping it alive and using correlation, try doing a
search on singleton orchestration in Google
http://groups.google.com/groups?hl=...br />
%3DSearch
"Michael Sparks sparksmail@bellsouth.net >" <<nospam/nospam> wrote in
message news:4B5E4DD6-4C0A-4D79-92E4-FACEFC40598B@microsoft.com...
> I have an implementation that should support allocating resources by
Orchestration. For example Orchestration A has higher priority than
Orchestration B. Orchestration B has a higher priority than Orchestration C
and so forth.
>
> Is there a way to control the number of simultaneous instances of a given
orchestration? Any recommendations on another approach that satifies the
throttling requirement are also welcome.
>
> TIA
|