locked
asp.net daily schedule service RRS feed

  • Question

  • User198012145 posted

    Hi,

        I am trying to figure out a way to maintain my daily schedule jobs which suppose to run midnight everyday and there are few jobs that run during the weekends. I want to maintain all those jobs from one place, I was looking into Quartz.net using "AdoJobStore" but due to very tight deadline I didn't have time to understand this.

    please suggest me what is the best way to maintain and create new schedule jobs in enterprise applications.

    thank you.

    Wednesday, November 28, 2018 12:51 AM

Answers

  • User-2054057000 posted

    Why don't you create APIs to do your job. Once api is live then you will get APIs enpoints which are URL that can be implemented in HTTP like:

    1. http:/www.somedomain.com/UpdateJob/1
    2. http:/www.somedomain.com/UpdateJob/2
    3. http:/www.somedomain.com/UpdateJob/3

    1, 2, 3 are the job id's which you will get in the web api C# method. And then in that method you add your custom logic of what the job has to do. 

    I think if you are just starting then it will take at least 3 days to complete this API job as you have to start from the very beginning.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, November 29, 2018 11:36 AM

All replies

  • User-821857111 posted

    If you have access to the server, you can create a console application that performs the task, and then use Windows Scheduler to get it to run when you want. If you don't have access to the server, you can use Quartz.NET, Hangfire.IO, Azure jobs (https://azure.microsoft.com/en-gb/services/scheduler/) or some other third party job management system.

    Wednesday, November 28, 2018 7:50 AM
  • User198012145 posted

    thank you for your replay, that's what we are doing using console application but we want to create one application to handle all jobs and provide webapi interface to interact with jobs.

    Wednesday, November 28, 2018 4:53 PM
  • User-2054057000 posted

    Why don't you create APIs to do your job. Once api is live then you will get APIs enpoints which are URL that can be implemented in HTTP like:

    1. http:/www.somedomain.com/UpdateJob/1
    2. http:/www.somedomain.com/UpdateJob/2
    3. http:/www.somedomain.com/UpdateJob/3

    1, 2, 3 are the job id's which you will get in the web api C# method. And then in that method you add your custom logic of what the job has to do. 

    I think if you are just starting then it will take at least 3 days to complete this API job as you have to start from the very beginning.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, November 29, 2018 11:36 AM
  • User-1720901320 posted

     In this what you can do is you can create a console application that performs the task if you have access to the server, and then use Windows Scheduler to get it to run anytime.

    Thursday, November 29, 2018 12:12 PM
  • User198012145 posted

    thank you for your suggestion I will give it a try.

    Thursday, November 29, 2018 4:34 PM
  • User198012145 posted

    we are already running like this, now I found better way to mantain my 20+ daily schedule jobs.

    thank you

    Thursday, November 29, 2018 5:22 PM