| Table of Contents |
|---|
The JobScheduler is configured using the following files are used to configure the JobScheduler:
$SCHEDULER_HOME/bin/jobscheduler_environment_variables.(sh|cmd)$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_HOMEDATA/bin/jobscheduler_environment_variables.(sh|cmdconfig/reporting.hibernate.cfg.xml(database connection for Reporting data)
These files are configured during the JobScheduler setup , using the information entered at the time. In addition, you can create further three additional files to adjust the environment can be created.These are:
$SCHEDULER_HOME/user_bin/jobscheduler_environnment_variables(for the 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
...
- )
...
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.
...
7.4 The custom.js File
...
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.
...
The
...
jobscheduler_environment_variables.(sh|cmd)
...
File
The JobScheduler's start parameter and ID are set in this file.
In this file the start parameter and the ID of the JobScheduler are set.
| Info | ||
|---|---|---|
|
This file should not be changed because the changes after a JobScheduler Update may |
...
be lost. If environment variables need to be adjusted, then |
...
put them in a |
...
|
...
file |
...
as a template. |
...
must be executable on |
...
Unix® systems. |
The $SCHEDULER $SCHEDULER_HOME/bin/jobscheduler_environment_variables.sh file file is particularly relevant for Linux®Linux®/Unix® Unix systems because it contains the LD_LIBRARY_PATH or and $JAVA_HOMEis set, which HOME variables. These must be customized, modified if the JobScheduler should does not find the Java virtual machineVirtual Machine.
In this case the following error is logged in the the $SCHEDULER_DATA/logs/scheduler.log:
| Code Block | ||
|---|---|---|
| ||
[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 Note that if you modify the JobScheduler Id on Microsoft® Windows® Microsoft Windows then note that the corresponding JobScheduler service must be reinstalled.
| Code Block | ||||
|---|---|---|---|---|
| ||||
$SCHEDULER_HOME/bin/jobscheduler.cmd remove $SCHEDULER_HOME/bin/jobscheduler.cmd install |
The sos.ini File
The $SCHEDULER_DATA/config/sos.ini file contains the license key for the JobScheduler. 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.
The factory.ini File
E-mail settings, information about the JobScheduler's 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.
The scheduler.xml File
Information about the JobScheduler ports and allowed hosts is to be found in the $SCHEDULER_DATA/config/scheduler.xml file.
Further details about this file are to be found here.
| Anchor | ||||
|---|---|---|---|---|
|
The custom.js File
The $SCHEDULER_DATA/config/operations_gui/custom.js file is used by JobScheduler Operations Center (JOC).
| Display feature availability | ||
|---|---|---|
|
Among the information specified in this file are the language and filter settings.
See also here for more details.
| Anchor | ||||
|---|---|---|---|---|
|
The hibernate.cfg.xml File
The $SCHEDULER_DATA/config/hibernate.cfg.xml file is used by:
- some of the JITL Jobs
- the JobScheduler Information Dashboard (JID) to get the database connection.
...
Display feature availability EndingWithRelease 1.11
See also the Dashboard documentation for more details.
| Anchor | ||||
|---|---|---|---|---|
|
The reporting.hibernate.cfg.xml File
The $SCHEDULER_DATA/config/reporting.hibernate.cfg.xml file is used by the JobScheduler and the JOC Cockpit to access the reporting database if a separate reporting database was specified during installation.
| Display feature availability | ||
|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
The jobeditor_environment_variables File
In this file the environment of The JobScheduler Object Editor (JOE) can be setenvironment is specified in this file.
You start JOE is started with $SCHEDULER_HOME/bin/jobeditor.(sh|cmd). This file should not be changed because the changes after a JobScheduler Update may have been lostchanges may be lost after an update of the JobScheduler. 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 file. You can use the file $SCHEDULER_HOME/user_bin/jobeditor_environment_variables.(sh|cmd)-example file as a template.
$SCHEDULER_HOME/user_bin/jobeditor_environment_variables must be executable on Unix®Unix systems.
The dashboard_environment_variables.(sh|cmd) File
In this file the environment of The JobScheduler Information Dashboard (JID) can be set.environment is specified in this file.
| Display feature availability | ||
|---|---|---|
|
JID is started with the You start JID with $SCHEDULER_HOME/bin/dashboard.(sh|cmd) file but this file should not be changed because the changes after a JobScheduler Update may have been lostchanges may be lost after an update of the JobScheduler. 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) file.
You can use the file $SCHEDULER_HOME/user_bin/dashboard_environment_variables.(sh|cmd)-example file as a template.
$SCHEDULER_HOME /user_bin/dashboard_environment_variables.(sh|cmd) must be executable on Unix®Unix systems.