isis-module-quartz

This module, intended for use with Apache Isis, provides a wrapper around the Quartz scheduler.

How to configure/use

You can either use this module "out-of-the-box", or you can fork this repo and extend to your own requirements.

"Out-of-the-box"

To use "out-of-the-box":

• update your classpath by adding this dependency in your webapp's project’s pom.xml:
  

  <dependency>
      <groupId>org.isisaddons.module.quartz</groupId>
      <artifactId>isis-module-quartz-dom</artifactId>
      <version>1.14.0</version>
  </dependency>

"Out-of-the-box" (-SNAPSHOT)

If you want to use the current -SNAPSHOT, then the steps are the same as above, except:

• when updating the classpath, specify the appropriate -SNAPSHOT version:
  

  <version>1.15.0-SNAPSHOT</version>

• add the repository definition to pick up the most recent snapshot (we use the Cloudbees continuous integration service). We suggest defining the repository in a <profile>:
  

  <profile>
      <id>cloudbees-snapshots</id>
      <activation>
          <activeByDefault>true</activeByDefault>
      </activation>
      <repositories>
          <repository>
              <id>snapshots-repo</id>
              <url>http://repository-estatio.forge.cloudbees.com/snapshot/</url>
              <releases>
                  <enabled>false</enabled>
              </releases>
              <snapshots>
                  <enabled>true</enabled>
              </snapshots>
          </repository>
      </repositories>
  </profile>

Forking the repo

If instead you want to extend this module’s functionality, then we recommend that you fork this repo. The repo is structured as follows:

• pom.xml - parent pom

• dom - the module implementation, depends on Isis applib

Usage

There are many ways to configure Quartz; the instructions below are for a basic setup:

• First, add an entry in web.xml:
  

  <servlet>
       <servlet-name>QuartzInitializer</servlet-name>
       <servlet-class>org.quartz.ee.servlet.QuartzInitializerServlet</servlet-class>
       <init-param>
           <param-name>config-file</param-name>
           <param-value>config/quartz.properties</param-value>
       </init-param>
       <init-param>
           <param-name>shutdown-on-unload</param-name>
           <param-value>true</param-value>
       </init-param>
       <init-param>
           <param-name>start-scheduler-on-load</param-name>
           <param-value>true</param-value>
       </init-param>
       <load-on-startup>1</load-on-startup>
  </servlet>

• Second, add a config/quartz.properties file:
  

  org.quartz.scheduler.instanceName = SchedulerQuartzConfigXml
  org.quartz.threadPool.threadCount = 1
  org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore
  org.quartz.plugin.jobInitializer.class = org.quartz.plugins.xml.XMLSchedulingDataProcessorPlugin
  org.quartz.plugin.jobInitializer.fileNames = config/quartz-config.xml
  org.quartz.plugin.jobInitializer.failOnFileNotFound = true

• Finally, add a config/quartz-config.xml file (also under in src/main/resources so is loaded from classpath):
  

  <?xml version="1.0" encoding="UTF-8"?>
  <job-scheduling-data
      xmlns="http://www.quartz-scheduler.org/xml/JobSchedulingData"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.quartz-scheduler.org/xml/JobSchedulingData http://www.quartz-scheduler.org/xml/job_scheduling_data_1_8.xsd"
      version="1.8">
  
      <schedule>
          <job>
              <name>RunBackgroundJobs</name>
              <group>DemoApp</group>
              <description>Runs all background jobs</description>
              <job-class>org.isisaddons.module.quartz.dom.jobs.RunBackgroundCommandsJob</job-class>
              <job-data-map>
                  <entry>
                      <key>user</key>
                      <value>scheduler_user</value>
                  </entry>
                  <entry>
                      <key>roles</key>
                      <value>admin_role</value>
                  </entry>
              </job-data-map>
          </job>
  
          <trigger>
              <cron>
                  <name>RunBackgroundJobsEvery10Seconds</name>
                  <job-name>RunBackgroundJobs</job-name>
                  <job-group>DemoApp</job-group>
                  <cron-expression>0/10 * * * * ?</cron-expression>
              </cron>
          </trigger>
  
      </schedule>
  </job-scheduling-data>

Details on the cron format can be found, for example, in this tutorial. For example:

• 0 0/30 * * * ? is every 30 minutes

• 0/10 * * * * ? is every 10 seconds

Change Log

• 1.14.0 - released against Isis 1.14.0

• 1.13.0 - released against Isis 1.13.0

Legal Stuff

License

Copyright 2016 Dan Haywood

Licensed under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Maven deploy notes

Only the dom module is deployed, and is done so using Sonatype’s OSS support (see user guide).

Release to Sonatype’s Snapshot Repo

To deploy a snapshot, use:

pushd dom
mvn clean deploy
popd

The artifacts should be available in Sonatype’s Snapshot Repo.

Release an Interim Build

If you have commit access to this project (or a fork of your own) then you can create interim releases using the interim-release.sh script.

The idea is that this will - in a new branch - update the dom/pom.xml with a timestamped version (eg 1.14.0.20160227-0738). It then pushes the branch (and a tag) to the specified remote.

A CI server such as Jenkins can monitor the branches matching the wildcard origin/interim/* and create a build. These artifacts can then be published to a snapshot repository.

For example:

sh interim-release.sh 1.14.0 origin

where

• 1.14.0 is the base release

• origin is the name of the remote to which you have permissions to write to.

Release to Maven Central

The release.sh script automates the release process. It performs the following:

• performs a sanity check (mvn clean install -o) that everything builds ok

• bumps the pom.xml to a specified release version, and tag

• performs a double check (mvn clean install -o) that everything still builds ok

• releases the code using mvn clean deploy

• bumps the pom.xml to a specified release version

For example:

sh release.sh 1.14.0 \
              1.14.0-SNAPSHOT \
              dan@haywood-associates.co.uk \
              "this is not really my passphrase"

where

• $1 is the release version

• $2 is the snapshot version

• $3 is the email of the secret key (~/.gnupg/secring.gpg) to use for signing

• $4 is the corresponding passphrase for that secret key.

Other ways of specifying the key and passphrase are available, see the `pgp-maven-plugin’s documentation).

If the script completes successfully, then push changes:

git push origin master && git push origin 1.15.0

If the script fails to complete, then identify the cause, perform a git reset --hard to start over and fix the issue before trying again. Note that in the dom’s `pom.xml the nexus-staging-maven-plugin has the autoReleaseAfterClose setting set to true (to automatically stage, close and the release the repo). You may want to set this to false if debugging an issue.

According to Sonatype’s guide, it takes about 10 minutes to sync, but up to 2 hours to update search.