WORK IN PROGRESS
Currently JobScheduler shipped with a proprietary built-in web server. Using the JobScheduler plugin feature it is possible to configure JobScheduler for working with Jetty. This document describes what you have to do, to run JobScheduler with an underlaying Jetty web server.
Installation
Now we have a "full" installer and an update installer with jetty. It is only a test version with the snapshot JobScheduler 1.3.12.2020-SNAPSHOT.
The update installer expects an existing installation.
The installer tries to generate some symlinks to simulate virtual directories for JOC (JobScheduler Operations Center). The symlink generation is not supported for Windows older than Vista.
The installer configures the ./config/factory.ini, the ./config/scheduler.xml, the ./config/live/jetty.xml and the ./config/live/web.xml as described below. The installer contains a keystore file for testing https. This keystore is not trusted and has a wrong hostname inside, but can still be used for testing.
Please make your own keystore file jetty.jks.
After the installation you can open JOC with jetty via
<span ih1. "classpath">
Configure factory.ini (Put the necessary libraries in the classpath)
To run JobScheduler with Jetty instead the built-in web-server you have to use the "Jetty plugin". It is a part of the library .:jetty-xxx.jar:.. Beside the .:jetty-xxx.jar:. it is necessary to put the dependend libraries for the jetty plugin into the classpath of the JobScheduler. The best place is to put them into the .:lib:. folder. If you use another folder, you have to add it to your classpath (see factory.ini).
</span>
<span id"scheduler">
Configure scheduler.xml
To use the jetty plugin you have to configure it in the scheduler.xml:
{{
<spooler>
<source>
<config ...>
<plugins>
...
<plugin java_class="com.sos.scheduler.engine.plugins.jetty.JettyPlugin">
<plugin.config />
</plugin>
...
</plugins>
...
</config>
</source>
</spooler>
}}
Please note that it is necessary to specify an empty plugin.config element.
</span>