...
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 customized, modified if the JobScheduler does not find the Java Virtual Machine.
...
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 then note that the JobScheduler service must be reinstalled.
Code Block | ||||
---|---|---|---|---|
| ||||
$SCHEDULER_HOME/bin/jobscheduler.cmd remove $SCHEDULER_HOME/bin/jobscheduler.cmd install |
The sos.ini
File
In the file The $SCHEDULER_DATA/config/sos.ini
contains 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.
...
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 changes may be lost after an update of the JobScheduler may be lost. 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.
Display feature availability | ||
---|---|---|
|
JID is started with the $SCHEDULER_HOME/bin/dashboard.(sh|cmd)
file but this file should not be changed because the changes changes may be lost after an update of the JobScheduler may be lost. 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.