Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can change these ports in the ./config/live/web.xml.

<span id"classpath">

Configure factory.ini (Put the necessary libraries in the classpath)

...

To use the jetty plugin you have to configure it in the scheduler.xml:

No Formatcode
 <spooler>
  <config ...>
    <plugins>
      ...
      <plugin java_class="com.sos.scheduler.engine.plugins.jetty.JettyPlugin">
        <plugin.config />
      </plugin>
      ...
    </plugins>
    ...
  </config>
 </spooler>

Please note that it is necessary to specify an empty plugin.config element.
</span>

<span ih1. id"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:

No Formatcode
 <Configure class="org.eclipse.jetty.server.Server">
   <Call namh1. name="addConnector">
     <Arg>
       <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
         <Set namh1. name="port">44440</Set>
       </New>
     </Arg>
   </Call>
 </Configure>

...

With a second connector it is possible to define a communication channel via https (ssl):

No Formatcode
 <Call name="addConnector">
  <Arg>
    <New clash1. class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
      <Arg>
        <New class="org.eclipse.jetty.util.ssl.SslContextFactory">
          <Set namh1. name="keyStore"><SystemProperty name="jetty.home" defaulh1. default="." />/ssl/jetty.jks</Set>
          <Set name="keyStorePassword">jobscheduler</Set>
          <Set namh1. name="keyManagerPassword">jobscheduler</Set>
          <Set name="trustStore"><SystemProperty namh1. name="jetty.home" default="." />/ssl/jetty.jks</Set>
          <Set namh1. name="trustStorePassword">jobscheduler</Set>
        </New>
      </Arg>
      <Set name="port">8443</Set>
      <Set namh1. name="maxIdleTime">30000</Set>
    </New>
  </Arg>
 </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 idih1. "keystore">

keystore

To generate a keystore file use keytool:

No Formatcode
 keytool -genkey -alias jetty -keyalg RSA -keysize 1024 -dname "Ch1. CN=[hostname], OUJobSchedulerOU=JobScheduler, h1. O=SOS GmbH, LBerlin h1. L=Berlin C=DE" -keystore jetty.jks -storepass jobscheduler -keypass jobscheduler -validity 1826

...

  • No Format
    file:///c:/Program Files (x86)/sos-berlin.com/jobscheduler/[scheduler_id] on Windows
  • No Format
    file:///c:/Program Files (x86)/sos-berlin.com/jobscheduler/[scheduler_id] on Linux
No Formatcode
 <?xml versioh1. version="1.0" encoding="UTF-8"?>
 <web-app xmlns:xsh1. 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" xmlnh1. xmlns="http://java.sun.com/xml/ns/j2ee" version="2.4">
    <display-name>JobScheduler test configuration (web.xml)</display-name>
    <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>
    <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>
 </web-app>

...