Hello,

It seems in every BTS project I get there is always a "once a day"
operation that goes along with an orchestration and I still dont have a
good way to do it.

What I mean by that is that this time I have to keep a running 30 day
archive of files (check once every day, the 31st day's files get
deleted) and I want to couple this process to the orchestration,
without adding more orchestrations, batch files, schemas, et al.

In addition, I dont want to repeat a process thousands of times (every
time an orchestration runs) a day and only have it hit a target once.

I considered a decision shape that checks a variable of some sort to
indicate its the first call to the service of the day, maybe by
updating a business rule vocabulary variable or something, but now I
have another schema.

Does anyone have a cleaner solution for an issue like this?

Thanks!

[ Post a follow-up to this message ]

Have a look at this:

http://www.gotdotnet.com/workspaces...2-f6f0-4ae6-a3d
1-865c61f0bc7d

There is a "timer" implementation that allows you to do "something" at a set
interval or at a set time. The learning curve is pretty short, but you will
have to read the whole doc to get it. Basically, your adapter will send a
generic dummy message to the orchestration you want to run at the prescribed
interval. The message will simply kick-off the orchestration.

I use it for multiple scenarios in production. It works great.

C.


"BA" <biztalk.architect@gmail.com> wrote in message
news:1114580517.494742.19390@g14g2000cwa.googlegroups.com...
> Hello,
>
> It seems in every BTS project I get there is always a "once a day"
> operation that goes along with an orchestration and I still dont have a
> good way to do it.
>
> What I mean by that is that this time I have to keep a running 30 day
> archive of files (check once every day, the 31st day's files get
> deleted) and I want to couple this process to the orchestration,
> without adding more orchestrations, batch files, schemas, et al.
>
> In addition, I dont want to repeat a process thousands of times (every
> time an orchestration runs) a day and only have it hit a target once.
>
> I considered a decision shape that checks a variable of some sort to
> indicate its the first call to the service of the day, maybe by
> updating a business rule vocabulary variable or something, but now I
> have another schema.
>
> Does anyone have a cleaner solution for an issue like this?
>
> Thanks!
>

[ Post a follow-up to this message ]