|
Home > Archive > BizTalk Server General > July 2005 > Implementing an end of day process in BTS 2004
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Implementing an end of day process in BTS 2004
|
|
| mangas76@gmail.com 2005-07-20, 2:48 am |
| I am new to BTS and am wondering what is the best approach to implement
an EOD process. I would like the process to be fired at a configurable
time each day.
Any information would be greatly appreciated!
Thanks
| |
| Yossi Dahan 2005-07-20, 7:52 am |
| Currently the process will have to be scheduled outside BizTalk.
create your process, which starts by receiving a message, then use windows
scheduler (or any other scheduling tool) to schedule a daily task to pass
this message to the process, this could be via a file drop. calling a web
service etc...
Yossi Dahan
<mangas76@gmail.com> wrote in message
news:1121829483.283808.163330@g44g2000cwa.googlegroups.com...
>I am new to BTS and am wondering what is the best approach to implement
> an EOD process. I would like the process to be fired at a configurable
> time each day.
> Any information would be greatly appreciated!
>
> Thanks
>
| |
| Scott Colestock 2005-07-20, 5:50 pm |
| You could also consider designing an orchestration with a looping construct
that delays for a particular time length, and performs the EOD operation if
within a particular service window.
In this case, you would only need to start the orchestration once.
Scott Colestock
www.traceofthought.net
"Yossi Dahan" <yossi.dahan@NOSPAMPLEASEsabratech.co.uk> wrote in message
news:%23vUh3RQjFHA.3540@TK2MSFTNGP14.phx.gbl...
> Currently the process will have to be scheduled outside BizTalk.
> create your process, which starts by receiving a message, then use windows
> scheduler (or any other scheduling tool) to schedule a daily task to pass
> this message to the process, this could be via a file drop. calling a web
> service etc...
>
> Yossi Dahan
>
> <mangas76@gmail.com> wrote in message
> news:1121829483.283808.163330@g44g2000cwa.googlegroups.com...
>
>
| |
| Patrick Chouinard 2005-07-26, 7:56 am |
| If I understand your question correctly, you would like the EOD process to
start at different hours everyday, with no particular pre establish schedule.
In that case most scheduling tools will not work for you.
-First option: Manual launch with a startup file
This is a very crude method but it work. You simply create an orchestration
that activate on the reception of a simple message (could be a one tag XML
document) and then execute your EOD process. This would require that somebody
manually activate the process by sending the startup document (remember
scheduling the sending of the startup document would not result in a fully
day to day custom schedule).
- Second Option: Using the BTSServiceWindows for BizTalk Server 2004
This solution assumes that you at least know a little bit in advance the
schedule time at which you want to start the EOD process. The
BTSServiceWindows utility is a custom scheduling component for BizTalk; it's
free and can be downloaded from GotDotNet user samples section:
http://www.gotdotnet.com/Community/...6F-AC4D25A6AFBB
This scheduling engine is based on an XML configuration file so the only
thing you need to do is create a simple user interface to modify the config
file to your desire scheduled time for the current day and your process will
start accordingly. If you don't need to change the schedule everyday but in
term can find a pattern in your scheduling, this component is very versatile
in term of complex schedule, so you should not have any problems to create
your custom schedule with it.
I hope this help.
--
Patrick Chouinard
BPI Analyst
http://www.cactuscommerce.com
"mangas76@gmail.com" wrote:
> I am new to BTS and am wondering what is the best approach to implement
> an EOD process. I would like the process to be fired at a configurable
> time each day.
> Any information would be greatly appreciated!
>
> Thanks
>
>
|
|
|
|
|