...
- how to download the JobScheduler engine binaries from Maven Central,
- the structure of the binaries,
- how to setup a minimal JobScheduler with the binaries.
Prerequisites
- JobScheduler artifacts are available from http://mvnrepository.com/artifact/com.sos-berlin/jobscheduler.engine starting with release 1.9.6.
- In order to download the binaries and to integrate them in your application it is required that you have Maven installed.
Maven
- Check the Maven Documentation.
- Download the latest Maven release
- Maven's
/bin
folder has to be added to the global variable "PATH
" in order to take effect. - No further configuration is required for Maven in order to compile. For individual configuration, for example to receive certain 3rd Party libraries from a Maven2 repository, e.g. http://repo1.maven.org/maven2, you have to configure the settings.xml file.
...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
[spooler] ; enable job history, if set to True the scheduler keeps a job history in database tables history = yes ; store job protocol for task history (yes|no|gzip, default: no) history_with_log = gzip ; store job protocol for order history (yes|no|gzip, default: no) order_history_with_log = gzip ; store protocol for scheduler history (yes|no|gzip, default: no) history_archive = gzip ; database configuration examples for job history ; active configuration db = jdbc -class=org.mariadb.jdbc.Driver jdbc:mysql://localhost:3306/scheduler -user=DB_USER -password=DB_USER_PASSWD db_class = SOSMySQLConnection ; sample configuration for MySQL ;db = jdbc -class=com.mysql.jdbc.Driver jdbc:mysql://localhost:3306/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSMySQLConnection ; sample configuration for MySQL via mariaDB ;db = jdbc -class=org.mariadb.jdbc.Driver jdbc:mysql://localhost:3306/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSMySQLConnection ; sample configuration for Oracle ;db = jdbc -class=oracle.jdbc.driver.OracleDriver jdbc:oracle:thin:@//localhost:1521/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSOracleConnection ; sample configuration for Microsoft SQL Server ;db = jdbc -class=com.microsoft.sqlserver.jdbc.SQLServerDriver jdbc:sqlserver://localhost:1433;sendStringParametersAsUnicode=false;selectMethod=cursor;databaseName=scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSMSSQLConnection ; sample configuration for Microsoft SQL Server via jTDS ;db = jdbc -class=net.sourceforge.jtds.jdbc.Driver jdbc:jtds:sqlserver://localhost:1433;sendStringParametersAsUnicode=false;selectMethod=cursor;databaseName=scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSMSSQLConnection ; sample configuration for Postgres SQL ;db = jdbc -class=org.postgresql.Driver jdbc:postgresql://localhost:5432/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSPgSQLConnection ; sample configuration for Firebird ;db = jdbc -class=org.firebirdsql.jdbc.FBDriver jdbc:firebirdsql://localhost:3050/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSFbSQLConnection ; sample configuration for DB2 ;db = jdbc -class=com.ibm.db2.jcc.DB2Driver jdbc:db2://localhost:50000/scheduler:driverType=2;retrieveMessagesFromServerOnGetMessage=true; -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSDB2Connection ; sample configuration for Sybase ;db = jdbc -class=com.sybase.jdbc3.jdbc.SybDriver jdbc:sybase:Tds:localhost:5000/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSSybaseConnection ; sample configuration for Sybase via jTDS ;db = jdbc -class=net.sourceforge.jtds.jdbc.Driver jdbc:jtds:sybase://localhost:5000/scheduler -user=DB_USER -password=DB_USER_PASSWD ;db_class = SOSSybaseConnection ; log level (info|debug1|...|debug9, default: info) log_level = info ; log directory log_dir = logs ; log filename and log categories (see http://www.sos-berlin.com/doc/en/scheduler.doc/factory_ini_spooler.xml#entry_log) log = PATH/TO/YOUR/logs/scheduler.log [java] class_path = PATH/TO/YOUR/3rdPartyLibraries/*.jar; ; put your Java VM parameters here options = -Dlog4j.configuration="file:///PATH/TO/YOUR/log4j.properties" ; enable detailed Java debug messages debug = no |
Noteinfo |
---|
For this example, we created a We set the class path in the factory.ini like this:
Otherwise an absolute path to the folder where the 3rd party libraries are copied to has to be configured. |
Create a file scheduler.xml
and configure the port your JobScheduler should listen to:
...