...
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>
<span id=ih1. "jetty">
Configure jetty.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). The minimal declaration defines a connector for the port to communicate with JobScheduler via http:
{{
<Configure class="org.eclipse.jetty.server.Server">
<source>
<Call name="addConnector">
<Arg>
<New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
<Set name="port">44440</Set>
</New>
</Arg>
</Call>
</source>
</Configure>
}}
It is important to know that this port (here 44440) is a substitute for the port attribute in the config element of scheduler.xml.
With a second connector it is possible to define a communication channel via https (ssl):
{{
<Call name="addConnector">
<source>
<Arg>
<New class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
<Arg>
<New class="org.eclipse.jetty.util.ssl.SslContextFactory">
<Set name="keyStore"><SystemProperty name="jetty.home" default="." />/ssl/jetty.jks</Set>
<Set name="keyStorePassword">jobscheduler</Set>
<Set name="keyManagerPassword">jobscheduler</Set>
<Set name="trustStore"><SystemProperty name="jetty.home" default="." />/ssl/jetty.jks</Set>
<Set name="trustStorePassword">jobscheduler</Set>
</New>
</Arg>
<Set name="port">8443</Set>
<Set name="maxIdleTime">30000</Set>
</New>
</Arg>
</source>
</Call>
}}
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 id"keystore">
keystore
To generate a keystore file use keytool:
keytool -genkey -alias jetty -keyalg RSA -keysize 1024 -dname "CN=hostname, OU=JobScheduler, O=SOS GmbH, L=Berlin C=DE" -keystore jetty.jks -storepass jobscheduler -keypass jobscheduler -validity 1826
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).
You must configure the JOC servlet with the JobScheduler installation path. Note that you must use the file protocol.
For Example:
No Format file:///c:/Program Files (x86)/sos-berlin.com/jobscheduler/[scheduler_id] on WindowsNo Format file:///c:/Program Files (x86)/sos-berlin.com/jobscheduler/[scheduler_id] on Linux
{{<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
<source>
xmlns="http://java.sun.com/xml/ns/j2ee"
version="2.4"
</source>
>
<source>
<display-name>JobScheduler test configuration (web.xml)</display-name>
</source>
<source>
<servlet>
<servlet-name>Default</servlet-name>
<servlet-class>org.eclipse.jetty.servlet.DefaultServlet</servlet-class>
<init-param>
<param-name>dirAllowed</param-name>
<param-value>false</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>Default</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
</source>
<source>
<servlet>
<servlet-name>JOC</servlet-name>
<servlet-class>org.eclipse.jetty.servlet.DefaultServlet</servlet-class>
<init-param>
<param-name>resourceBase</param-name>
<param-value>file:///c:/Program Files (x86)/sos-berlin.com/jobscheduler/scheduler</param-value>
</init-param>
</servlet>
<servlet-mapping>
<servlet-name>JOC</servlet-name>
<url-pattern>/operations_gui/*</url-pattern>
</servlet-mapping>
</source>
</web-app>}}
</span>