The JobScheduler is configured using the following files:
$SCHEDULER_DATA/config/sos.ini$SCHEDULER_DATA/config/factory.ini$SCHEDULER_DATA/config/scheduler.xml$SCHEDULER_DATA/config/operations_gui/custom.js(for JOC)$SCHEDULER_DATA/config/hibernate.cfg.xml(database connection of JID)$SCHEDULER_HOME/bin/jobscheduler_environment_variables.(sh|cmd)
These files are configured during the JobScheduler setup, using the information entered at the time. In addition, you can create further three files to adjust the environment.These are:
$SCHEDULER_HOME/user_bin/jobscheduler_environnment_variables(for JobScheduler)$SCHEDULER_HOME/user_bin/jobeditor_environment_variables(for JOE)$SCHEDULER_HOME/user_bin/dashboard_environment_variables(for JID)
7.1 The sos.ini File
In the file $SCHEDULER_DATA/config/sos.ini the license key is included. In addition, Java options and if necessary the location of the Java® Virtual Machine (JVM) can be configured.
Further details about the entries in this file are to be found here.
7.2 The factory.ini File
E-mail settings, information about the database connection and the Java archives classpath are saved in the $SCHEDULER_DATA/config/factory.ini file.
Further details about the entries in this file are to be found here.
7.3 The scheduler.xml File
The JobScheduler port information is to be found in the $SCHEDULER_DATA/config/scheduler.xml file.
Further details about this file are to be found here.
7.4 The custom.js File
The $SCHEDULER_DATA/config/operations_gui/custom.js file is used by JobScheduler Operations Center (JOC). Beside other settings you can configure the language and filters in particular.
See also here for more details.
7.5 The hibernate.cfg.xml File
The $SCHEDULER_DATA/config/hibernate.cfg.xml file is used by JobScheduler Information Dashboard (JID) to get the database connection.
See also the Dashboard documentation for more details.
7.6 The jobscheduler_environment_variables.(sh|cmd) File
In this file the start parameter and the ID of the JobScheduler are set.
This file should not be changed because the changes after a JobScheduler Update may have been lost. If environment variables need to be adjusted, then please put them in a file $SCHEDULER_HOME /user_bin/jobscheduler_environnment_variables. You can use the file $SCHEDULER_HOME /user_bin/jobscheduler_environment_variables.(sh|cmd)-example as a template. $SCHEDULER_HOME /user_bin/jobscheduler_environnment_variables must be executable on Unix®.
The $SCHEDULER_HOME/bin/jobscheduler_environment_variables.sh file is particularly relevant for Linux®/Unix® systems because the LD_LIBRARY_PATH or $JAVA_HOMEis set, which must be customized, if the JobScheduler should not find the Java virtual machine.
In this case the following error is logged in the $SCHEDULER_DATA/logs/scheduler.log:
[ERROR Z-JAVA-100 Java Virtual Machine cannot be loaded [0509-022 Cannot load module ... System error: A file or directory in the path name does not exist.] [libjvm.so]]
If you modify the JobScheduler Id on Microsoft® Windows® then note that the corresponding service must be reinstalled.
$SCHEDULER_HOME/bin/jobscheduler.cmd remove $SCHEDULER_HOME/bin/jobscheduler.cmd install
7.7 The jobeditor_environment_variables File
In this file the environment of JobScheduler Object Editor (JOE) can be set.
You start JOE with $SCHEDULER_HOME/bin/jobeditor.(sh|cmd). This file should not be changed because the changes after a JobScheduler Update may have been lost. If environment variables (e.g. $JAVA_HOME) need to be adjusted, then please put them in a file $SCHEDULER_HOME/user_bin/jobeditor_environment_variables. You can use the file $SCHEDULER_HOME/user_bin/jobeditor_environment_variables.(sh|cmd)-example as a template.
$SCHEDULER_HOME/user_bin/jobeditor_environment_variables must be executable on Unix®.
7.8 The dashboard_environment_variables.(sh|cmd) File
In this file the environment of JobScheduler Information Dashboard (JID) can be set.
You start JID with $SCHEDULER_HOME/bin/dashboard.(sh|cmd) but this file should not be changed because the changes after a JobScheduler Update may have been lost. If environment variables (e.g. $JAVA_HOME) need to be adjusted, then please put them in a file $SCHEDULER_HOME /user_bin/dashboard_environment_variables.(sh|cmd).
You can use the file $SCHEDULER_HOME/user_bin/dashboard_environment_variables.(sh|cmd)-example as a template.
$SCHEDULER_HOME /user_bin/dashboard_environment_variables.(sh|cmd) must be executable on Unix®.