The JobScheduler Information Dashboard starts with the script:
- ./bin/dashboard.sh (Unix
- .\bin\dashboard.cmd /Windows)
JID is a SWT application.
The JobScheduler setup and the JID standalone setup contains the ./lib/swt.jar in a 32Bit version. You can change the ./lib/swt.jar to a 64Bit version (see below).
JID requires an Oracle Java Runtime Environment (JRE) at least version 1.7.x.
For AIX you can use the IBM Java Runtime Environment (JRE) at least version 1.7.x, too.
So, JID is tested only with these JREs.
Tests with openJRE are not finished, but until now we don't get an error.
JID requires on Unix a XULRunner 1.9.2, which must be set in the environment variable MOZILLA_FIVE_HOME (see http://www.eclipse.org/swt/faq.php#browserlinuxrcp).
XULRunner versions >= 2.0 do problems, which Mozilla and SWT must resolve among themselves.
JID with 32Bit
In this case you need a 32Bit JRE, a 32Bit XULRunner (on Unix) and a 32Bit SWT (already containing in the setup).
Unix
1. Make sure that a 32Bit Oracle or IBM JRE is used.
The JID startscript reads the Java Environment from the ./user_bin/dashboard_environment_variables.sh script.
You find an example ./user_bin/dashboard_environment_variables.sh-example. Rename this file to ./user_bin/dashboard_environment_variables.sh and make sure that it is executable.
Edit ./user_bin/dashboard_environment_variables.sh
... JAVA_HOME="/path/to/32bit-java-jre" ...
2. May be JID doesn't find the XULRunner. In this case make sure that JID finds the XULRunner.
Edit ./user_bin/dashboard_environment_variables.sh. We assume that the XULRunner is stored in /usr/lib/xulrunner-1.9.2.
... MOZILLA_FIVE_HOME="/usr/lib/xulrunner-1.9.2" ...
Windows
Make sure that a 32Bit Oracle JRE is used.
The JID startscript reads the Java Environment from the .\user_bin\dashboard_environment_variables.cmd script.
You find an example .\user_bin\dashboard_environment_variables.cmd-example. Rename this file to .\user_bin\dashboard_environment_variables.cmd.
Edit .\user_bin\dashboard_environment_variables.cmd.
... JAVA_HOME="C:\Program Files(x86)\java\jre6" ...
If you start JID with a 64Bit Java JRE and a 32Bit SWT then it cannot open the GUI.
Unfortunately, no error is seen because the startscript calls javaw.exe in a new window.
Since Release 1.3.12.1248 you can call the startscript with the parameter debug to see errors, e.g.:
C:\Program Files (x86)\sos-berlin.com\...\bin>dashboard.cmd debug
JID with 64Bit
In this case you need a 64Bit JRE, a 64Bit XULRunner (on Unix) and a 64Bit SWT.
1. Download a 64Bit SWT from http://www.eclipse.org/swt/ and copy it to ./lib instead of the already existing 32Bit SWT.
Unix
2. Make sure that a 64Bit Oracle or IBM JRE is used.
The JID startscript reads the Java Environment from the ./user_bin/dashboard_environment_variables.sh script.
You find an example ./user_bin/dashboard_environment_variables.sh-example. Rename this file to ./user_bin/dashboard_environment_variables.sh and make sure that it is executable.
Edit ./user_bin/dashboard_environment_variables.sh
... JAVA_HOME="/path/to/64bit-java-jre" ...
3. May be JID doesn't find the XULRunner. In this case make sure that JID finds the XULRunner.
Edit ./user_bin/dashboard_environment_variables.sh. We assume that the XULRunner is stored in /usr/lib64/xulrunner-1.9.2.
... MOZILLA_FIVE_HOME="/usr/lib64/xulrunner-1.9.2" ...
Windows
2. Make sure that a 64Bit Oracle JRE is used.
The JID startscript reads the Java Environment from the .\user_bin\dashboard_environment_variables.cmd script.
You find an example .\user_bin\dashboard_environment_variables.cmd-example. Rename this file to .\user_bin\dashboard_environment_variables.cmd.
Edit .\user_bin\dashboard_environment_variables.cmd.
... JAVA_HOME="C:\Program Files\java\jre6" ...
If you start JID with a 32Bit Java JRE and a 64Bit SWT then it cannot open the GUI.
Unfortunately, no error is seen because the startscript calls javaw.exe in a new window.
Since Release 1.3.12.1248 you can call the startscript with the parameter debug to see errors, e.g.:
C:\Program Files (x86)\sos-berlin.com\...\bin>dashboard.cmd debug