Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

The JobScheduler requires an Oracle Java JRE (version >= 1.6).

You can install a JRE for exclusive use by Job Scheduler.
This could be useful if, for example, you have already installed a JRE that is used with another application and you want that JRE to remain unchanged and not be used by JobScheduler.

Note that the procedure described below should be followed before JobScheduler is installed.

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.

Now you can configure this new JRE to be used by JobScheduler:

Windows

Assume that you have extracted the new JRE into C:\ProgramData\jre and
you have extracted the JobScheduler download to %TEMP%.

Normally you start the installer with %TEMP%\jobscheduler<version>\setup.cmd
This script looks in the registry to get the JRE, where it finds the JRE that has already been installed and not the one to be used by JobScheduler.

To get around this, open a command line as administrator and type the following:

 > cd %TEMP%\jobscheduler&lt;version&gt;
 > set Path=C:\ProgramData\jre\bin;%Path%
 > java.exe -jar jobscheduler_win32.jar

The JobScheduler setup will now use the new JRE in C:\ProgramData\jre and write this JRE in the following files:

  • ./bin/jobscheduler_environment_variables.cmd
 ...
 if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
 ...
  • ./bin/jobeditor_environment_variables.cmd
 ...
 if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
 ...
  • ./bin/dashboard_environment_variables.cmd
 ...
 if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
 ...

Note that the above will only cause the new JRE to be used if JAVA_HOME has not been set.
Otherwise you have to create the following files:

  • ./user_bin/jobscheduler_environment_variables.cmd
  • ./user_bin/jobeditor_environment_variables.cmd
  • ./user_bin/dashboard_environment_variables.cmd
    and then insert
 set JAVA_HOME=C:\ProgramData\jre

in them.

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.

 ...
 [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

Linux

WORK IN PROGRESS

  • No labels