| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
WORK IN PROGRESSPROGRESSh1. > this document is not yet linked in the Index of the wiki
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.
...
<span ih1. id"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 idih1. "scheduler">
Configure scheduler.xml
...
Please note that it is necessary to specify an empty plugin.config element.
</span>
<span ih1. id"jetty">
Configure jetty.xml
...
The SSL connection expects the jetty keystore file jetty.jks in the subfolder ssl (under the JobScheduler data folder). With the configuration above you can connect JobScheduler via https at port 8443.
</span>
<span idih1. "keystore">
keystore
To generate a keystore file use keytool:
...
whereas hostname should be the JobScheduler host.
</span>
<span id="web">
Configure web.xml
To run JobScheduler with jetty it is also necessary to create two configuration files for the Jetty web server (jetty.xml and web.xml). It has to place in the root of your live folder (not in the config folder).
...