Is it possible for user who access my page to run a schedule task in asp.net? any reference?
The page can turn on a flag to run a scheduled process, than a windows service can be setup to monitor that flag (stored in DB or file), when its turned on, run the process.
HTH.
ASP.NET itself can't run a scheduled task, but you can use Powershell or Windows Task Scheduler to queue up and schedule tasks to be run at a later time.
If you want a user to be able to alter them it would probably be easiest to have a task set to call a special ASP.NET page which would then run any logic needed to actually do the tasks scheduled by users.
If you have a SQL database backend, you can always create SQL Agent jobs to run and use your ASP.net application to control them. (When to start, frequency, etc)
Related
I am working on an asp.net mvc-5 web application, deployed under windows 2012 & iis-8. my asp.net mvc have many CRUD operations which are implemented as action methods inside my asp.net mvc.
But my asp.net mvc web application will be doing scheduled long running network scan process, the network scan will mainly do the following steps:-
Get the list of our servers and vms from our database.
Get the scanning username and password for each server and vm from a third party tool, using Rest API.
Call some powershell scripts to retrieve the servers & vms info such as network info, memory, name, etc.
Update our ERP system with the scan info using Rest API.
Now I did a pilot project using the following approach:-
I define a Model method inside my asp.net mvc to do the above 4 steps.
Then I install hangfire tool which will be calling the scan method on predefined scheduler.
Also I create a View inside my asp.net mvc which allow users to set the hangfire schedule settings (this require to do an IIS reset on the host server for hangfire to get the new settings).
Now I run a test scan for a round 150 servers which took around 40 minutes to complete , and it worked well. The only thing I noted is that if I set the schedule to run on non-business hours (where no activity is made on IIS) then hangfire will not be able to call the job, and once the first request is made the missed jobs will run. I overcome this limitation by defining a windows task which calls IIS each 15 minutes, to keep application pool live, and it worked well...
Now the other approach I am reading about is doing my above is as follow:-
Instead of defining Model method inside asp.net mvc to do the scan, I can create a separate console application to do the scan.
Then inside my asp.net mvc to create a view which allow users to create and schdule a task inside the windows tasks scheduler. I can do so by integrating with the windows task scheduler API.
Where this windows task will be calling the console application.
Now I am not sure which approach is better and why ? now generally speaking long running/background jobs should not run under iis.. But at the same time defining these long running processes as console app and calling these apps inside windows task scheduler will create extra dependencies on my web application. And will add extra effort when moving the application from move server to another (for example from test to live)..
Beside this I read that tools such as hangfire, quartz and other are designed to allow running long running tasks inside IIS and they eliminate the need to create console applications and scheduling these console applications using task scheduler ..
So can anyone advice on this?
In my opinion, if it is possible to solve the scheduling problem on the web application side, there is no need to create a scheduler task or a new console application for triggering purposes. The problem you will probably face when using scheduling task in a web application is generally common as you might see is that: The scheduler works like a charm during debugging of the web application, but not being able to trigger after publishing it to IIS. At this point the problem is generally related to IIS rather than the schedulers Quartz.NET, Hangfire, etc. Although there are lots of articles or solution methods posted on the web, unfortunately only some of them is working properly. In addition to this, most of them require lots of configuration settings on the web and machine configuration.
However, there are also some kind of solutions for such a kind of scheduling problem and I believe in that it is worthy to give a try Keep Alive Service For IIS 6.0/7.5. Just install it on the server to which you publish your application and enjoy. Then your published application will be alive after application pool recycling, IIS/Application restarting, etc. That is also used in our MVC application in order to send notification mails weekly and has been worked for months without any problem. Here are the sample code that I use in our MVC application. For more information please visit Scheduled Tasks In ASP.NET With Quartz.Net and Quartz.NET CronTrigger.
*Global.asax:*
protected void Application_Start()
{
JobScheduler.Start();
}
*EmailJob.cs:*
using Quartz;
public class EmailJob : IJob
{
public void Execute(IJobExecutionContext context)
{
SendEmail();
}
}
*JobScheduler.cs:*
using Quartz;
using Quartz.Impl;
public class JobScheduler
{
public static void Start()
{
IScheduler scheduler = StdSchedulerFactory.GetDefaultScheduler();
scheduler.Start();
IJobDetail job = JobBuilder.Create<EmailJob>().Build();
ITrigger trigger = TriggerBuilder.Create()
.WithIdentity("trigger1", "group1")
.StartNow()
.WithSchedule(CronScheduleBuilder
.WeeklyOnDayAndHourAndMinute(DayOfWeek.Monday, 10, 00)
//.WithMisfireHandlingInstructionDoNothing() //Do not fire if the firing is missed
.WithMisfireHandlingInstructionFireAndProceed() //MISFIRE_INSTRUCTION_FIRE_NOW
.InTimeZone(TimeZoneInfo.FindSystemTimeZoneById("GTB Standard Time")) //(GMT+02:00)
)
.Build();
scheduler.ScheduleJob(job, trigger);
}
}
Also I create a View inside my asp.net mvc which allow users to set the hangfire schedule settings (this require to do an IIS reset on the host server for hangfire to get the new settings).
You're resetting your webserver to update a task's schedule? That doesn't sound healthy. What you might do is keep track of what the scheduled time should be, and on execution, check if the current time is within a certain range of the scheduled time (or has already been executed), otherwise abort the job.
The only thing I noted is that if I set the schedule to run on non-business hours (where no activity is made on IIS) then hangfire will not be able to call the job, and once the first request is made the missed jobs will run. I overcome this limitation by defining a windows task which calls IIS each 15 minutes, to keep application pool live, and it worked well...
Hangfire's documentation has a page about running delayed tasks that mentions what you need to change to accomodate this.
Using Windows' Task Scheduler doesn't seem like a good idea; it's not meant for the execution of ad-hoc, short-lived tasks. You probably need elevation to create tasks, and you'd probably need to define another scheduled task to clean up the mountain of tasks that would exist after a few dozen background jobs have been executed.
You're also correct that using Windows' Task Scheduler would make it more difficult to move your application around.
I am planning to create an asp.net mvc web application which will perform a single sync job, to achieve this:-
We have a 3rd party ERP system which will be generating a .csv file on timely basis, where it will generates a .csv file once per hour. The .csv file contain info about our company assets, such as type, price, name ,location, etc…
Now i will develop an asp.net mvc web application which will read the .csv data and update a database with this data.
So I am planning to do the following :-
I will create a new database, which will contain the data.
I will create a new asp.net mvc-5 web application which have a SYNC action method, which will read the .csv data, and update the database.
now the problem I am facing is that I need the sync job to run per hour or on a specific schedule. Now from my previous experience I can list these 2 approaches to call an action method on timely basis:-
Inside the asp.net mvc ‘s global.asax I can create a schedule which runs each hour.
I can use third party tools such as Hangfire to schedule the tasks.
Now using any of these approaches will cause this limitation:-
The global.asax or the third party tools such as Hangfire will run under the application pool, and if no action is performed on the application, then the schedule will never run, since the application pool will not be active. But on my previous applications this was not a real problem as the systems contained many views beside the schedule jobs , so the system stay active almost 100% over working hours.
But in my current project the web application will not be accessed by users, since it will only do a single sync job, and there is not any other functionalities for end users. so in this case the sync job will never run , since the application pool will not be active.
So can anyone advice if these approaches sound valid to fix my problem:-
To create a windows schedule task which will be calling the action method URL per hour:-
schtasks /create /tn "my scheduled task" /tr "powershell
-ExecutionPolicy unrestricted -Command \"(New-Object Net.WebClient).DownloadString(\\http://url
.to.be.executed/cron.php\\")\" /sc DAILY /st 07:00:00 /ru System
To create 2 schedule tasks inside the global.asax . one schedule task will call the application url each 5 minutes to keep the application pool alive, and another schedule task which call the sync action method each hour. In this case the application will keep calling itself every 5 minutes which will force the application pool to say alive and the sync job will run each hour even if no users access the system …
So can anyone advice on this please?
Thanks
MVC is all about user interaction, and many users interacting with the same application at that. If all you need is one task to be run on a schedule, then you don't even need a UI for that, and there's no issues of needing to handle multiple simultaneous remote requests or such that a web application satisfies. You could literally just create a console app and use Windows Task Scheduler. MVC is complete overkill, and more than that, unsuited to the purpose.
In my project I required to write some background jobs for scheduled processing. I did it using quartz scheduler with spring, but quite often it required me to execute the tasks at random without schedule. So later I pulled out the tasks from the quartz and created web endpoints for them(exposed internally).
To perform the regular scheduled based operation of tasks, I created unix cron jobs that hit the web endpoints using curl command.
My question is, why could this approach not work always. Even in case you don't want to expose web endpoints, you can always execute standalone tasks using unix cron. Is there any particular advantage I gain by using quartz scheduler over unix cron jobs?
You may still opt for using Quartz if:
An event needs to be scheduled as part of the activity that happens within the java application itself. For example, user subscribes to a newsletter.
You have a listener object that needs to be notified when the job completes.
You are using JTA transactions in your scheduled job
You want to keep the history of job executions or load job and trigger definitions from a file or a database
You are running on an application server and require load balancing and failover
You are not running on an UNIX / Linux environment (i.e. you wanted platform independence)
I have a function that takes about 2-3 minutes to do all of the processing it needs
It only needs to do the calculations once daily. The processing is done inside of a background thread that is started inside Application_Start in Global.asax.cs.
I am worried that the application will kill the method while it is running.
You are doing the process in in Application_Start, are you restarting your application daily ?. A better approach would be to create a separate executable for the task, and schedule it on your server using Windows Scheduler.
For the above scenario, either you can use windows service or console application and schedule it when you want it to run.
But doing it at the start of application is never recommended in this scenario.
I want to run an event periodically on the server side that is to be initiated by the server in ASP.NET scenario. There will be no request from client.
Your help will be much appreciated.
Assuming you have access to the server and can install external applications, you could create a stand-alone Windows Service or even a console application that is triggered by the built in Windows Task Scheduler.
For something that runs in Asp.Net you could use Quartz.net. This SO question explains how to use it with Asp.Net
You need to spawn a process using the Process class. The process will sleep until the recurrence time comes.
Process p = new Process();
p.StartInfo.FileName = "foo";
p.Start();
Another alternative is to spool a thread using the Thread class.
For a similar situation in some of the applications, I use a separate service (windows service/web service) and use System.Threading.Timer (see http://msdn.microsoft.com/en-us/library/system.threading.timer.aspx) and implement a scheduler of my own. Or otherwise, you can use any server based standard scheduler to invoke some executable that in turn hits your service.
I would just create a standard command line executable and have it run with the Windows Scheduling Tool.
A windows service is fine if it runs in very short intervals, but for example for once a day task, I think its the wrong approach.
Have a look at the Windows Workflow Foundation
That framework is built for this kind of things, like state persistance etc. It also runs separate, so the process will not go down when your app(pool) goes down (by default due to IIS).
Integrates fully with asp.net and you'll probably end up (in a positive way) with a Delay Activity.