Our production environment is designed for high availability, It will include a master-authoring server and 2 web-servers using DFS to update from master-authoring to web servers.
What is the best way to deal with Scheduled tasks?
In my case it's a simple task that moves events from a 'current' folder to a 'past' folder. The move also triggers an event to remove the registration form on the event.
Ideally it would be ideal to have authoring and web servers have the same configuration files. I could configure the scheduled task to begin with 'http://localhost...' (which I couldn't if it was shared hosting.)
Will this work?
If the authoring server is the only server with scheduled tasks I'm guessing the changes it publishes will push to the web-servers ok, however I'm concerned the authoring server may be not running and the app. It may not even be initialised because it's visited far less frequently than the web-servers.
Scheduled Tasks in a load balanced environment
Our production environment is designed for high availability, It will include a master-authoring server and 2 web-servers using DFS to update from master-authoring to web servers.
What is the best way to deal with Scheduled tasks?
In my case it's a simple task that moves events from a 'current' folder to a 'past' folder. The move also triggers an event to remove the registration form on the event.
Ideally it would be ideal to have authoring and web servers have the same configuration files. I could configure the scheduled task to begin with 'http://localhost...' (which I couldn't if it was shared hosting.)
Will this work?
If the authoring server is the only server with scheduled tasks I'm guessing the changes it publishes will push to the web-servers ok, however I'm concerned the authoring server may be not running and the app. It may not even be initialised because it's visited far less frequently than the web-servers.
Thoughts? Suggestions?
Cheers.
Murray.
is working on a reply...