Product Knowledge Base

Space shortcuts

Page tree

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_DATA/config/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, 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)

The jobscheduler_environment_variables.(sh|cmd) File

The JobScheduler's start parameter and ID are set in this file.

Important

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 $SCHEDULER_HOME /user_bin/jobscheduler_environnment_variables file. 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® systems.

The $SCHEDULER_HOME/bin/jobscheduler_environment_variables.sh file is particularly relevant for Linux®/Unix systems because it contains the LD_LIBRARY_PATH and $JAVA_HOME variables. These must be modified if the JobScheduler does 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]]

 

Note that if you modify the JobScheduler Id on Microsoft Windows then the JobScheduler service must be reinstalled.

Example: Reinstall the JobScheduler service
$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.

The custom.js File

The $SCHEDULER_DATA/config/operations_gui/custom.js file is used by JobScheduler Operations Center (JOC). FEATURE AVAILABILITY ENDING WITH RELEASE 1.11

Among the information specified in this file are the language and filter settings.

See also here for more details.

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.  FEATURE AVAILABILITY ENDING WITH RELEASE 1.11

See also the Dashboard documentation for more details.

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.  FEATURE AVAILABILITY STARTING FROM RELEASE 1.11  See also the JobScheduler Master Installation - 1 - Database Configuration article for more details.

The jobeditor_environment_variables File

The JobScheduler Object Editor (JOE) environment is specified in this file.

JOE is started with $SCHEDULER_HOME/bin/jobeditor.(sh|cmd). This file should not be changed because the changes 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 $SCHEDULER_HOME/user_bin/jobeditor_environment_variables file. You can use the $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 systems.

The dashboard_environment_variables.(sh|cmd) File

The JobScheduler Information Dashboard (JID) environment is specified in this file.  FEATURE AVAILABILITY ENDING WITH RELEASE 1.11

JID is started with the $SCHEDULER_HOME/bin/dashboard.(sh|cmd) file but this file should not be changed because the changes 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 $SCHEDULER_HOME /user_bin/dashboard_environment_variables.(sh|cmd) file.

You can use the $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 systems.