...
The following archive files including installer are available from the SOS Web-Site and from Source Forge:
jobscheduler_linux-x64.[release].tar.gzfor Linux 64-Bitjobscheduler_linux-x86.[release].tar.gzfor Linux 32-Bitjobscheduler_windows-x64.[release].zipfor Microsoft Windows 64-Bitjobscheduler_windows-x86.[release].zipfor Microsoft Windows 32-Bit
...
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 it you will require an X-Server. Use Batch Installation if an X-Server is not available.
...
The setup requires administrator privileges on Microsoft Windows. The setup opens will open a dialog for this on Microsoft Windows if necessary. On Unix a sudo prompt will be open. Don't log in as root on Unix but use sudo! .
Under Unix, root privileges are not required. If you want to install the JobScheduler without root privileges, then call:
| Code Block | ||||
|---|---|---|---|---|
| ||||
/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.
For the rest of this documentation the first installation directory will be referred to as $SCHEDULER_HOME and the second as $SCHEDULER_DATA.
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.
The JobScheduler Operations Center (JOC) interface 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.
...
The JobScheduler is available with a dual licensing model. The : the GNU GPL 2.0 license and a commercial license is are available for Microsoft Windows and Linux.
...
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 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 isvalues for this path are:
/opt/sos-berlin.com/jobschedulerfor Unix®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\jobschedulerfor Microsoft® Windows®Microsoft® Windows®
Step 6: The Configuration and Log File Path
The configuration and log files are stored in this second ($SCHEDULER_DATA) pathpath, which will be referred to as $SCHEDULER_DATA in the rest of this installation guide. The default isvalues for this path are:
/home/[user]/sos-berlin.com/jobschedulerfor UnixC:\ProgramData\sos-berlin.com\jobschedulerfor Microsoft Windows Vista/2008/7C:\Documents and Settings\All Users\Application Data\sos-berlin.com\jobschedulerfor Microsoft Windows XP/2003
| Anchor | ||||
|---|---|---|---|---|
|
...
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 like such as / \ : ; * ? ! $ % & " < > ( ) | ^
- The ID is used on Microsoft Windows for 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 (except you want to build a cluster). Further, the JobScheduler ID expands both installation paths as a sub-directory. (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_HOMEand$SCHEDULER_DATAinstallation 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 with the JobScheduler e.g. to send operating information 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 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 See also the How to operate JobScheduler with Jetty article for more details about Jetty. Host and Port entries are written to the
$SCHEDULER_DATA/config/scheduler.xmlfile 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_hostdocumentation. - The Port and the Allowed Host entries are entry is also written to the
$SCHEDULER_DATA/config/scheduler.xmlfile.
- 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
- 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.xmlfile. The configuration files can be- file and can be changed manually later on.
Mail and SMTP Configuration
The SMTP Server is specified here along the mail sender, recipient and if required CC und BCC recipients if required. Multiple addresses are to be separated by commas.
The values entered here configure Values entered in this form are saved in the $SCHEDULER_DATA/config/factory.ini file, which can also be changed manually later on.
Mail Notification & Event Handling
Specify information regarding whether 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. It enables the JobScheduler 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. Corresponding Relevant objects will be created in $SCHEDULER_DATA /config/live/sos/events respectively folder. This is explained in more detail in the Events documentation.
| Anchor | ||||
|---|---|---|---|---|
|
...
The Database Support Package Forms
...
Standalone / Cluster Configuration
The radio buttons in the form shown above determine whether the architecture in which the JobScheduler should is to be installed. The following options are available:
- "stand-alone"
...
- as part of a backup system
...
- or
- as part of aload-balancing cluster.
See (see also JobScheduler Master Installation - 10 - Installation of a Cluster. Further information about Backup Cluster can be found here, about Load Balancing look here.
You can change the cluster option architecture later (see here).
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 is remains checked, so that a the script which creates and fills the necessary database tables can be executed. Alternatively, the tables can be be changed manually later on (page 28). If on. If you have already installed another JobScheduler with JobScheduler with the same database connection then abandon uncheck this option.
Database Connection
The database connection information is access parameters are specified in the input fields. The middle part where you can choose the provided jTDS JDBC® driver 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 DBMS driver to be used is specified in the middle part of the form:
- The jTDS JDBC
®driver delivered with the JobScheduler is only shown for Sybase® and
...
- Microsoft SQL Server®.
- If you selected MySql® then you get a checkbox for alternatively use of the
...
- MariaDB® JDBC® driver.
- If you do not check the jTDS
...
- JDBC® or the MariaDB JDBC driver then you must enter your own
...
- JDBC® driver in a later form.
The database connection next dialog. This configuration is saved in the $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.
...