OpenJUMP Configuration
General Notes
- There exists two different possibilities of configuring JUMP. On one hand there are the Java Virtual Machine options which have to be put directly behind the _javaw_ argument if starting JUMP. On the other hand there are start options of JUMP itself which have to be set after the call of JUMPWorkbench
- There are two (or more) options on starting JUMP.. one provided with the original JUMP distribution for windows is clicking the JUMP icon. The other option is to use the openjump.bat file (for Unix users: openjump.sh) part of the OpenJUMP distribution.
- In the first case you can do the modifications below by right mouse click on the icon and go to Properties, and change to the Shortcut tab. Now modify the text in "Target" box.
- In the second case you edit the bat file with a text editor.
How to set the memory usage of JUMP?
You just modify this by adding -Xmx -Xms parameters either
- in the batch file if you use this one to start JJUMP or
- if you use the Windows Icon to start: Right Click on the icon and go to _Properties_, and change to the _Shortcut_ tab. Now modify the text in "Target" box. (it may be useful to make a copy of the text or icon first)
eg. "C:\Program Files\Java\jre1.5.0_06\bin\javaw.exe" -Xms256M -Xmx512M -jar "C:\Program Files\Jump\jump.jar" -properties "C:\Program Files\Jump\workbench-properties.xml" -plug-in-directory "C:\Program Files\Jump\lib\ext"
In this example a minimum of 256M memory and at max 512 MB are allocated to JUMP.
The setting can be done in the startup file (e.g. openjump.bat). In general there are two options:
- either use the OpenJUMP option: *-i18n FR* at the end of the "start java" line. Here the language is set to french (abbreviation: FR)
- since the -i18n XX option does sometimes not work properly a second option exists. In your startup-file set directly behind "start javaw ...". -Duser.language=en_EN
before "com.vividsolutions.jump.workbench.JUMPWorkbench -properties ..." or en_GB or en_US. Note the underscore between en_EN.
How to change the Skin (Layout) of JUMP?
use the following arguments right behind calling "start javaw ..." in the batch file or from command line
-Dswing.defaultlaf=javax.swing.plaf.metal.MetalLookAndFeel -Dswing.defaultlaf=javax.swing.plaf.windows.WindowsLookAndFeel
How to ensure that external plugins (i.e. extensions) are loaded
check if the start option *-plug-in-directory %LIB%/ext* is used
if it is used, you may also add to your startup script (e.g. the openjump.bat file) _;%%LIB%%/ext_ to the end of the CLASSPATH (window$)
How to set the path of the workbench-state.xml file?
use the following argument in the batch file or from command line:
-state "putHereFilePath"
the default value is to $HOME/.jump/ (similar as for workbench-properties file)
note: a) this argument does not work for the log-file b) the argument is implemented from nightly-built 26th August 2007 on
OpenJUMP looks by default for the file called default-plugins.xml contained in the /bin/ folder. This file defines which functions from the tool menu are loaded. The OpenJUMP option is called for development purposes this way:
-default-plugins c:\dev\eclwork\openjump_svn\scripts\default-plugins.xml
which is similar to using the '-properties' option
How to open a default project when OpenJUMP is started
You can open a default project the first time OpenJUMP is started. The path to your project must be defined by the -project option in the .bat or in the .sh starting script.
-project C:\path\to\project\myproject.jmp
or
-project ..\myfolder\myproject.jmp
Optimizing Java for speed (Linux Environment)
If you're editing large datasets using also large rasters as I do you'll appreciate these two flags when starting Java: -server -XX:+UseBiasedLocking
At the end of your 'openjump.sh' change the line to read: $JAVA -server -XX:+UseBiasedLocking -cp $CLASSPATH:$JUMP_HOME/bin $JAVA_OPTS $MAIN $JUMP_OPTS $
From the documentation: -XX:+UseBiasedLocking Enables a technique for improving the performance of uncontended synchronization. An object is "biased" toward the thread which first acquires its monitor via a monitorenter bytecode or synchronized method invocation; subsequent monitor-related operations performed by that thread are relatively much faster on multiprocessor machines. Some applications with significant amounts of uncontended synchronization may attain significant speedups with this flag enabled; some applications with certain patterns of locking may see slowdowns, though attempts have been made to minimize the negative impact.
HTH Pedro Doria Meunier