[Building Sakai] JobScheduler

[John Bush]

The job stuff in sakai is just quartz, if you start learning about
that maybe it will make more sense.  Quartz provides an interface
called "Job" which you implement.  Then you wire it up in spring to
give it a name and bring in your dependencies.  Then you use the tool
to create a trigger to schedule it.

http://quartz-scheduler.org/documentation

Look at some examples.

Here's our SIS loading job that we've been running for years:

https://source.sakaiproject.org/svn/msub/rsmart.com/sakai/trunk/rsmart/customer/customer-int-impl/src/java/com/rsmart/customer/integration/job/IntegrationJob.java

Wire it up in Spring:

https://source.sakaiproject.org/svn/msub/rsmart.com/sakai/trunk/rsmart/customer/customer-int-comp/src/webapp/WEB-INF/components.xml

You can expose properties to jobs now too, that was added here:
https://jira.sakaiproject.org/browse/SAK-13696

That is nice if you don't want to restart sakai to change some
properties, like maybe a term, or in this case file names.

Look at the Configurable SIS Synchronization job in the spring config
above for an example with more detail.

On Fri, Sep 27, 2013 at 6:18 AM, sangeetha d <sangee1229 at gmail.com> wrote:
> Hi,
>
>    This is Sangeetha.Now,I m currently exploring Job Scheduler in sakai
> module.I learnt how to create jobs and triggers in sakai documentation.But i
> need some clarification in that.What job will run behind the code normally
> and why we creating new job, type for that job and trigger for new job in
> job scheduler tool.And kindly explain me about 'Quartz'. Could You Please
> clarify my doubts and send some related documents.
>
> Thanks & Regards,
> D.Sangeetha
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
> with a subject of "unsubscribe"



-- 
John Bush
602-490-0470

** This message is neither private nor confidential in fact the US
government is storing it in a warehouse located in Utah for future
data mining use cases should they arise. **