Page History

...

Anchor
setup setup

1.1 Installation Using the Setup Program

The following archive files including installer are available from the SOS Web-Site and from Source Forge:

...

/tmp/jobscheduler.[release]> ./setup.sh -u

Procedure Overview

The setup dialog starts with the selection of the language to be used in the setup. This is followed by a greeting, acceptance of the license conditions and the specification of the two installation directories required. The binaries and libraries are stored under the first path.The configuration and log files are stored under the second path.

...

• http://localhost:[port]/joc/ where [port] is the HTTP/HTTPS 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 and a commercial license are 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 JobScheduler ID will be entered later on.

Step 5: The Installation Path

The binaries and libraries are stored in this first path, which will be referred to as $SCHEDULER_HOME in the rest of this installation guide. The default values for this path are:

•  /opt/sos-berlin.com/jobscheduler for Unix^®. If you use the installer without root permissions then you must choose another folder (e.g. /home/[user]/sos-berlin.com/jobscheduler). 
• C:\Program Files\sos-berlin.com\jobscheduler for Microsoft^® Windows^®

Step 6: The Configuration and Log File Path
Image Modified 

The configuration and log files are stored in this second path, which will be referred to as $SCHEDULER_DATA in the rest of this installation guide. The default values for this path are:

...

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 and the database configuration.

Network Configuration

• The JobScheduler ID

  • The JobScheduler ID is entered in the JobScheduler ID input box. Omit special characters such as  / \ : ; * ? ! $ % & " < > ( ) | ^
  • The ID is used on Microsoft Windows as 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. (Unless you are building a cluster, in which case all JobScheduler Masters have the same ID. See JobScheduler Master Installation - 10 - Installation of a Cluster for more information.)
  • In addition, the JobScheduler ID is used as a subdirectory name in the both the $SCHEDULER_HOME and $SCHEDULER_DATA installation paths.
  • The JobScheduler ID is written to the $SCHEDULER_HOME/bin/jobscheduler_environment_variables.(cmd|sh) file and can be changed manually later on.

• The JobScheduler Host and Ports

  • The JobScheduler Host is used for TCP and HTTP/HTTPS communication to send operating information for JOC and 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 for HTTP and HTTPS communication by the JobScheduler Web Services. 

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

  • The Host and Port entries are written to the $SCHEDULER_DATA/config/scheduler.xml file and can be changed manually later on.

• 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 Allowed Host entry is also written to the $SCHEDULER_DATA/config/scheduler.xml file and can be changed manually later on.

Mail and SMTP Configuration

The SMTP Server is specified here along the mail sender, recipient and CC und BCC recipients if required. Multiple addresses are to be separated by commas.

Values entered in this form are saved in the $SCHEDULER_DATA/config/factory.ini file, which can be changed manually later on.

 Mail Notification & Event Handling

Specify the conditions under which the JobScheduler should automatically forward job log files by e-mail. 

...

The JobScheduler Database Package Forms

Standalone / Cluster Configuration

The radio buttons in the form shown above determine the architecture in which the JobScheduler Master is to be installed. The following options are available:

...

You can change the architecture later (see here).

The JobScheduler Database Management System

The database system is specified in the upper selection on this form. It is recommended that the box in the center of the form remains checked, so that the script which creates and fills the necessary database tables can be executed. Alternatively, the tables can be be changed manually later on. If you have already installed another JobScheduler with the same database connection then uncheck this option.

The JobScheduler Database Connection

The database access parameters are specified in the upper part of the form. These are saved in the $SCHEDULER_DATA/config/factory.ini file, which can also be changed manually later on.

...

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 was 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.

The Reporting Database Package Forms

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

...