Demo Access Instructions

Demo Access Instructions

The demo has been configured to provide 24 unique Quartz scheduler connections. These connections allow you to access various versions of Quartz schedulers embedded in our test web applications that are all deployed alongside the QuartzDesk web application (QuartzDesk GUI) on the same Tomcat container.

To save system resources, we have disabled some of the test web applications and therefore their respective scheduler connections are inactive. These inactive connections are displayed in light-gray color - please see the figure below.

Registered Quartz Schedulers.

All of the test web applications used in the demo can be downloaded from GitHub.

To start experimenting with a particular Quartz scheduler instance, please double-click on its connection and a new scheduler view will open with multiple tabs where you can see the list of all jobs and triggers running in the selected scheduler. Please note there are two types of test jobs available in the demo:

 

Job ClassDescription
com.quartzdesk.test.quartz.vX.TestJobNon-interruptible test job implementation.
com.quartzdesk.test.quartz.vX.InterruptibleTestJobInterruptible test job implementation.

 

The X in the job class package name is either 1 for Quartz 1.8.x schedulers, or 2 for Quartz 2.x schedulers. The difference between these two job implementation can be observed in the "Currently Executing Jobs" tab where jobs implemented by the InterruptibleTestJob can be interrupted, whereas jobs implemented by the TestJob class cannot be interrupted. 

All test jobs that are based on the above-mentioned job classes support the following job data map parameters that can be passed to the jobs when they are ad-hoc executed from the QuartzDesk GUI. These parameters can be used to test various QuartzDesk functionality because they alter test jobs' behavior to simulate various common situations that can occur during job execution (e.g. a job execution failure etc.).

 

Parameter NameDescription
exceptionMakes the job throw a job execution exception with an optional message passed in the parameter’s value. This parameter allows you to simulate job execution failures.
vetoMakes the Quartz scheduler to veto the job execution. This parameter allows you to simulate job execution vetoes.
sleepTimeMakes the job enter a busy wait loop that makes the job wait for the specified number of seconds before exiting the loop. This parameter allows you to simulate long running jobs because normally the execution of a test job takes only a few milliseconds.

This parameter is typically used to experiment with the "Currently Executing Jobs" tab.

resultMakes the job save the specified value as its job execution result. This parameter allows you to simulate jobs that produce an execution result.
userDataSimilar to result, but it is a QuartzDesk extension for scenarios when result cannot be used. You can think of the userData parameter as "result2".
interruptExceptionMakes the job throw a org.quartz.UnableToInterruptJobException when the job receives an interrupt request. This parameter allows you to simulate job execution scenarios when an interruptible job explicitely refuses an interrupt request by throwing the UnableToInterruptJobException from its interrupt method that is invoked to handle the interrupt request.

This parameter is only recognized by jobs implemented by the com.quartzdesk.test.quartz.vX.InterruptibleTestJob class.

 

The following figure shows an example of ad-hoc executing a job with 3 job data map parameters:

Job Ad-Hoc Trigger Parameters

 

Please Avoid

Because the QuartzDesk demo is a shared demo that can be used by multiple people who evaluate our product, please try to avoid the following actions that may interfere with actions performed by other demo users:

  • Deleting objects (e.g. notification rules, message channel profiles etc.) created by other users.

  • Entering sensitive data (e.g. passwords) in message channel profiles and notification rules because these objects can be accessed and used by other users. We suggest that you set up temporary test accounts (e.g. free GMail accounts) for these purposes.

 

Thank you.

If you have any questions or experience any issues, please let us know by submitting your query to This email address is being protected from spambots. You need JavaScript enabled to view it.. Thank you.