Sample/boilerplate web application using Quartz scheduler. It allows you to configure a set of http calls to made according to a schedule.
The calls to make and their schedule are configured in an XML file
src/main/resources/jobs.xml using the standard Quartz format.
The http calls to be made can be:
- GET
- POST with body in
jobs.xml - POST with body from file
- PUT with body in
jobs.xml - PUT with body from file
Http calls are made using Apache http client,
default timeouts and connection management are configured in scheduler.properties. The timeouts can be overridden
on a per job basis.
The status of the jobs (what was the result of last http call) and when their next invocation is planned can be accessed via '<app_url>/statusCheck'.
The application log can be accessed via '<app_url>/logs/log'.
The log levels can be controlled on a per job(-group) basis (each job has its own logger:
nl.hsac.scheduler.jobs.<job-group>.<job>). The job/trigger details are made available as MDC variables.
Logging is configured by updating logback.xml (see logback's configuration manual).
To run the scheduler, deploy the 'WAR' to a Java servlet engine (e.g. Jetty or Tomcat).
The easiest way to run the scheduler (after cloning) is via Maven using mvn jetty:run, which will start a Jetty instance
(listening on port 8080) running the scheduler. It can then be accessed on
http://localhost:8080/.
The scheduler can also be run as docker container using image hsac/scheduler:<version>.
The configuration can then be overridden by overwriting the config files (the same as present in src/main/resources) in
/jetty/webapps/ROOT/WEB-INF/classes.