| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The JobScheduler requires an Oracle Java JRE (version >= 1.6).
...
Start by downloading an Oracle JRE archive from http://www.oracle.com/technetwork/java/javase/downloads/index.html
- jre-<version>-linux-i586.tar.gz
- jre-<version>-windows-i586.tar.gz
Don't use the jre-
...
<version>linux-i586.rpm or
...
the jre<version>-windows-i586.exe archives.
You only have to extract this archive to an arbitrary folder to get a new JRE.
It is not necessary to make any changes to the original Java environment.
...
To get around this, open a command line as administrator and type the following:
| Code Block |
|---|
> cd %TEMP%\jobscheduler<version>
> set Path=C:\ProgramData\jre\bin;%Path%
> java.exe -jar jobscheduler_win32.jar
|
...
- ./bin/jobscheduler_environment_variables.cmd
| Code Block |
|---|
...
if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
...
|
- ./bin/jobeditor_environment_variables.cmd
| Code Block |
|---|
...
if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
...
|
- ./bin/dashboard_environment_variables.cmd
| Code Block |
|---|
...
if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
...
|
...
- ./user_bin/jobscheduler_environment_variables.cmd
- ./user_bin/jobeditor_environment_variables.cmd
- ./user_bin/dashboard_environment_variables.cmd
and then insert
| Code Block |
|---|
set JAVA_HOME=C:\ProgramData\jre
|
...
Finally, JobScheduler itself looks by default in the registry to find the JRE. To get JobScheduler to use the new one, configure the path to the jvm.dll of the new JRE installation in the ./config/sos.ini file and then restart the JobScheduler.
| Code Block |
|---|
...
[java]
; does not necessarily work, use PATH (Windows) or LD_LIBRARY_PATH (Unix) to locate the Java VM
vm = C:\ProgramData\jre\bin\client\jvm.dll
|
...