Page History

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

You can install a JRE for exclusive use by JobScheduler.
This is useful if, for example, if Sometimes 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 the that JRE to remain unchanged and not be used by 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 a 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-i586x64.tar.gz
• jre-<version>-windows-i586x64.tar.gz

Don't use

...

jre-

...

<version>linux-

...

x64.rpm or

...

jre<version>-windows-

...

x64.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 this configure the new JRE for the JobScheduler.to be used by JobScheduler:

Windows

We assume Assume that you have extracted the new JRE is extracted in to 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 up the JRE in the registry to get where it finds the current JRE.
But this is not the new JRE for the JobScheduler.JRE that has already been installed and not the one to be used by JobScheduler.

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

 > cd %TEMP%\jobscheduler&lt;version&gt;jobscheduler<version>
 > set Path=C:\ProgramData\jre\bin;%Path%
 > java rem don't use setup.cmd because it looks in the registry to find a jre
 > javaw.exe -jar jobscheduler_win32windows-x64.<version>.jar

Now the The JobScheduler setup will now use the new JRE in C:\ProgramData\jre and it writes the JRE in some files:write this JRE location to the ./bin/jobscheduler_environment_variables.cmd

...

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

• ./bin/jobeditor_environment_variables.cmd

file.

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

You see that the new JRE is only Note that the above will only cause the new JRE to be used if JAVA_HOME is unset has not been set.

Otherwise you have to createuse 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 insert

 set JAVA_HOME=C:\ProgramData\jre

There is one thing left to do.
The JobScheduler looks into the registry to find the JVM but you want to use another.
Configure in the ./config/sos.ini the path of Finally, JobScheduler itself by default looks up the JRE in the registry. To make JobScheduler use the new JRE, 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

...

Assume that you have extracted the new JRE to /opt/jre and that you have extracted the JobScheduler download to /tmp.

Normally you start the installer with /tmp/jobscheduler<version>/setup.sh.

This script uses the JRE that is specified with the JAVA_HOME environment variable otherwise Java is used from the path (see `which java`), therefore set JAVA_HOME=/opt/jre before you start the installer.

Code Block
> cd /tmp/jobscheduler<version> > export JAVA_HOME=/opt/jre > ./setup.sh

The JobScheduler setup will now use the new JRE from /opt/jre and write the JRE location to the ./bin/jobscheduler_environment_variables.sh file.:

Code Block
... test -z $JAVA_HOME && JAVA_HOME=/opt/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.sh
• ./user_bin/jobeditor_environment_variables.sh
• ./user_bin/dashboard_environment_variables.sh
  and then insert

Code Block
JAVA_HOME=/opt/jre # and further in ./user_bin/jobscheduler_environment_variables.sh LD_LIBRARY_PATH=$JAVA_HOME/lib/amd64/server:$LD_LIBRARY_PATH

in them.WORK IN PROGRESS