The best option to achive this , would be using Job Schedulers like cron .
Go through this cron and let me know , if you have any queries , because we implemented this way only in our previous Application .
Ravi Kiran Va wrote: The best option to achive this , would be using Job Schedulers like cron .
While cron is an option if Colin is on a *nix system (he doesn't specify). I don't know that I would call it the best option. I dislike having an external system that has to be maintained concurrently with the main system. Especially one that would have completely different setup instructions for the person deploying the system, and one that would introduce far more complexity in ensuring that there are no race conditions or conflicts in the two separate systems both modifying the same database tables and fields.
Personally I would look at the Timer class, or one of the packages that replace cron (e.g. cron4j, or quartz)