Page History

...

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

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

Further you want to provide that the existing java environment remains unchanged.

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

Start by downloading an Oracle JRE archive In this case you can download the archive of the Oracle JRE 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 jre<version>-windows-i586.exe

You only have to extract the this archive in to an arbitrary folder and you to get a new JRE without .
It is not necessary to make any changes in to the original Java environment.

Now you can use configure this new JRE for the JobScheduler.to be used by JobScheduler:

Windows

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

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

So take this way.
Please To get around this, open a command line as administrator and type the following:

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

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

• ./bin/jobscheduler_environment_variables.cmd

...

 ...
 if not defined JAVA_HOME set JAVA_HOME=C:\ProgramData\jre
 ... 

You see that Note that the above will only cause the new JRE is only to be used if JAVA_HOME is unsethas 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
  In these files you and then insert

 set JAVA_HOME=C:\ProgramData\jre

There is one thing left to doin them. The

Finally, JobScheduler looks into by default in the registry to find the JVM but you want JRE. To get JobScheduler to use another.
Configure in the ./config/sos.ini the path of 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.

...