Page History

...

Installation Using the Setup Program

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

...

The installer can be started as a dialog or in batch mode (see Batch Installation). If you use the installer as a dialog on Unix then you will require an X-Server. Use Batch Installation if an X-Server is not available.

...

/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 that are required. The binaries and libraries are stored under the first directory.The configuration and log files are stored under the second.

...

Specification of the installation directories is followed by the Package Selection dialog. The forms which are subsequently presented for the configuration of the JobScheduler depend on the packages which are selected for installation alongside the JobScheduler. Further details of the JobScheduler configuration are to be found in the Setup Forms section.

After selection of the required packages, the necessary files are copied into the installation directories. After this, the scripts that configure the installation packages are executed. The processing of the installation scripts run during the setup is logged. This log file is to be found in the folder $SCHEDULER_DATA/logs and is named Install_V[release]_[date][time]_[series number].log. 

...

• http://localhost:[port]/joc/ where [port] is the HTTP/HTTPS port specified for the JobScheduler instance during setup.

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.

...

Installation Paths

The setup requires the paths to two directories. A sub-directory named with the JobScheduler ID will then be added to both these directories later in the installation procedure. The JobScheduler ID will be entered later on.

Step 5: The Installation Path

The binaries and libraries are stored in this first directory, which will be referred to as $SCHEDULER_HOME in the rest of this installation guide. The default paths to this directory 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 directory, which will be referred to as $SCHEDULER_DATA in the rest of this installation guide. The default paths to this directory are:

...

Setup Packages

The following packages may be selected during setup:

...

Setup Forms

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

Network Configuration

• The JobScheduler ID

  • The JobScheduler ID is entered in the JobScheduler ID input box. Avoid special characters such as  / \ : ; * ? ! $ % & " < > ( ) | ^
  • The ID is used on Microsoft Windows as the name of the JobScheduler service after setup. The service name will have 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 - Cluster Installation 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 feature 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 in this form, along the mail sender, recipient and CC and BCC recipients if required. Multiple addresses are possible and should 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

This form is used to specify the conditions under which the JobScheduler should automatically forward job log files by e-mail. 

The entries made using this form are saved in the $SCHEDULER_DATA/config/factory.ini file, which can also be changed manually later on.

The lower part of this form is only shown when the Housekeeping Package was selected in the Setup Packages form and is used to specify whether the JobScheduler is to be configured as an event handler. Relevant objects will be created in $SCHEDULER_DATA /config/live/sos/events folder. This is explained in more detail in the Events documentation.

...

The JobScheduler Database Configuration 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 database tables can be be changed manually later on.

The JobScheduler Database Connection

The access parameters for the JobScheduler database are specified in the upper part of this form. The database connection configuration is saved in three locations: 

• $SCHEDULER_DATA/config/factory.ini
• $SCHEDULER_DATA/config/hibernate.cfg.xml and 
• $SCHEDULER_DATA/config/sos_settings.ini files. 

All files can be changed manually if required.

The DBMS driver to be used is specified in the middle part of the form:

...

Note that for IBM^® DB2 you have to provide a license file for the driver. 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 Configuration Forms

Reporting information can be stored in the same database as used by the JobScheduler Master, which was configured in the steps described above, or in a separate database, possibly using another DBMS.

...