Page History

The steps described below should be carried out when making a new installation of the JobScheduler, in the order presented below:

• Database Configuration
  • The JobScheduler Master requires a database. (Only the JobScheduler Agent can be operated without a database.) The JobScheduler needs the database to archive logs and to remember Job and Order states. A JobScheduler agent doesn't have own Jobs or Orders and the logging is made by the JobScheduler which calls the Agent. So an Agent is running without a database.
  • You find the supported database management systems listed in the Which Database Management Systems are supported by JobScheduler? article.
  • Because of licensing restrictions when used with MySql^®, Sybase or Microsoft^® SQL Server databases, a JDBC^® driver appropriate to the database version used must be provided by end users themselves. Alternatively, a jTDS JDBC^® driver, which is delivered with the JobScheduler setup, can be used for Microsoft SQL Server and Sybase databases. Similarly, the MariaDB^® driver is delivered with the JobScheduler setup and can be used for MySql Server and MariaDB databases. Drivers for Oracle^® Database and PostgreSQL are contained in the JobScheduler setup.
• JobScheduler Installation
  • Installation of the JobScheduler is carried out using a setup program. This can be downloaded from the SOS Web-Site for Microsoft Windows^® and Linux^®.
  • For more information see the Which platforms is JobScheduler available for and what platform support is provided? article.

...

1.1 Requirements

The JobScheduler Master is available for Linux and Microsoft Windows in 64-bit and 32-bit versions: the JobScheduler Universal Agent should be used for all other operating systems..

Requirements for the 64-Bit JobScheduler

• Oracle Java^® Runtime Environment (JRE) 64-Bit in version 1.8.x. For Unix^®: 

...

The JobScheduler requires some 64-Bit libraries.These are on Linux:

...

• libgtk-x11-2.0.so.0
• libXtst.so.6

• If you use "Remote Configuration" then the Workload JobSchedulers and its Supervisor JobScheduler should have the same version. Further information about "Remote Configuration" can be found in the Which components will be installed on a client and how will jobs be started there? article.

Requirements for the 32-Bit JobScheduler

• Oracle® Database Java® Runtime Environment (JRE) 32-Bit at least version 1.8.x.  
• For Unix^®: 

1. • linux-gate.so.1
   • libz.so.1
   • libpthread.so.0
   • libdl.so.2
   • libm.so.6
   • ld-linux.so.2

   Two JobScheduler components (the JobScheduler Object Editor, JOE, and JobScheduler Information Dashboard, JID,) are SWT applications and require an X-windows system and GTK2. The installation includes a 32-Bit swt.jar, but you still need the following 32-Bit libraries:

   • libgtk-x11-2.0.so.0
   • libXtst.so.6

• For Microsoft® Windows^®:

...

Anchor
setup setup

1.

...

1 Installation Using the Setup Program

The following archive files including installer are available:

...

JobScheduler Operations Center (JOC) can be accessed after the setup by entering the following URL in a web browser (Firefox , Microsoft Internet Explorer^®, Chrome^® are supported): http://localhost:[port] where [port] is the port specified for the JobScheduler instance during setup.

1.

...

2 Licenses

The JobScheduler is available with a dual licensing model. The GNU GPL 2.0 license is available for Microsoft Windows and Linux.

...

1.

...

3 Installation Paths

The setup requires two paths. A sub-directory named with the JobScheduler ID will then be added to both these paths. The form for entering the JobScheduler ID will be described later on.

...

1.

...

4 Setup Packages

The following packages may be selected during setup:

...

1.

...

5 Setup Forms

The number of forms shown during setup depends on the packages which have been chosen for installation.

1.

...

5.1 The Basic JobScheduler Forms

• The JobScheduler ID

  • The JobScheduler ID is entered in the JobScheduler ID input box. Omit special characters like  / \ : ; * ? ! $ % & " < > ( ) | ^
  • The ID is used on Microsoft Windows for the name of the JobScheduler service after setup. The service name has the syntax sos_scheduler_[scheduler_id].
  • The JobScheduler ID must be unique over all installed JobSchedulers (except you want to build a cluster). 
  • Further, the JobScheduler ID expands both installation paths as a sub-directory.

• The JobScheduler Host and Ports

  • The JobScheduler Host is used for TCP and HTTP/HTTPS communication with the JobScheduler e.g. for JOC and for the JobScheduler Web Services.
    • The JobScheduler Port is used for TCP communication with the JobScheduler i.e. for JOC.
    • The JobScheduler HTTP Port is used HTTP and HTTPS communication by the JobScheduler Web Services. 

      • This port must be unique for each JobScheduler Master being operated standalone or as a cluster member. 

      • The See also the How to operate JobScheduler with Jetty article for more details about Jetty. 

• The Allowed Host 

  • This field is required as a security feature of the JobScheduler, whereby communication can be restricted to particular computers. This is explained in more detail in the JobScheduler allowed_host documentation.
  • The Port and the Allowed Host entries are also written to the $SCHEDULER_DATA/config/scheduler.xml file.
• The JobScheduler ID is written to the $SCHEDULER_HOME/bin/jobscheduler_environment_variables.(cmd|sh) file.
• The ports for Jetty / the Web Services is written to the JobScheduler database $SCHEDULER_DATA/config/jetty.xml file. The configuration files can be changed manually later on.

...

1.

...

5.2 The Database Support Package Forms

The following forms are only shown when the Database Support package was selected.

...

The script for the creation of the database tables is started by the setup program and requires a JDBC® driver appropriate to the database system being used. The drivers for Oracle® Database and PostgreSQL are included in the setup. However, the relevant IBM® DB2, MySql®, Sybase and Microsoft® SQL Server JDBC® driver must be manually specified here. Note that for Microsoft® SQL Server and Sybase databases the jTDS JDBC® driver and for MySql® the MariaDB® JDBC® driver that is delivered as part of the JobScheduler setup can be used when the appropriate checkbox in the previous form is activated. For IBM® DB2 you have to provide a license file for the driver too. As this driver will also be required by the JobScheduler later on, it is copied by the setup into the $SCHEDULER_HOME /lib/user_lib folder.

1.5.3 The Reporting Database

Reporting information can be stored in the same database as used by the JobScheduler Master or in a a separate one. The check list for for specifying a DBMS for the reporting database will only be shown if the JobScheduler and Reporting Databases are the same box is unchecked. 

...