Jiggle Installation Instructions

Summary of what you need to run Jiggle:

  1. Create a valid Java runtime environment on your computer.

  2. If the Java Run-Time Environment (JRE) is not installed on your system, download and install the latest Java JRE or JDK. The JRE is the Java Runtime Environment. The JDK (Java Development Kit) is the JRE plus compilers and tools. The latest version of Jiggle with the Swarm option requires Java runtime 1.5 or higher.
    Download the latest Java release

  3. Create a directory for the Jiggle program and its libraries.

  4. The Jiggle application directory "folder" can be anywhere or a standard application directory:
    Unix : /usr/jiggle
    Windows : C:\Program Files\Jiggle

    For a quick setup download and unzip into a root directory of your choice:  jiggle16-client.zip
    Unzipping creates a directory named "Jiggle" below the root directory, and all .jar files and scripts are located in a /bin subdirectory, all properties files are located in a /props subdirectory, and all documentation files are located in a /doc subdirectory.

    After extraction, update the included jiggle.jar by downloading the appropriate jiggleTest.. jar (see links below) and rename the new file to jiggle.jar after deleting the old one. You do not need to download any other files.
    Included are example startup scripts for Unix (jiggle.command) and Windows (jiggle.bat). Edit these files, if necessary, to change java runtime reference, directory path variables, or input property filename. Once the application is started using a script, a popup dialog will prompt you for your local network code and the database connection values if they are undefined in the properties file. Channel data are read from a disk cache file, and if it does not already exist, a database query will build it; however, the query does take quite a while to process, so be patient.

  5. Download the appropriate jiggle jar file and put it in the application directory created above  (Version Release Notes).

  6. The "Beta build" version below is the latest code build. Whatever jar version you download, you should rename it to match your startup (script) command reference jar filename.

    Latest version: Version 2014-4-30 and later require change to Origin.type column constraint in db

    The ORACLE JDBC jar: ojdbc7.jar must be used with Jiggle jar files below.

     Java8 jiggle18-p7.jar (2017-06-27)

     Java7 jiggle18-p7g.jar for GTYPE enabled schema only (2017-06-27)

    The ORACLE JDBC jar: ojdbc6.jar must be used with Jiggle jar files below.

     Java7 jiggle17-p6g.jar for GTYPE enabled schema only (2017-06-27)

     Java7 jiggle16-p6g.jar for GTYPE enabled schema only (2017-06-27)

     Java7 jiggle17-p6.jar (2017-06-27)

     Java6 jiggle16-p6.jar (2017-06-27)

        NOTE: when using these Jiggle jars with existing command scripts, replace references to ojdbc14.jar with ojdbc6.jar. The 'p6' jars have ojdbc6.jar in their manifest classpath.

    NOTE: option to use 2 new database tables: EVENTPREFOR and ORGPREFPRIORITY. If enabled, these tables must exist, and a new ORGPREF package and the latest EPREF package must be installed in the database. To enable the option, user adds the property "useEventPreforTable=true" to his properties file. The Jiggle jars will work with your existing database schema with this option disabled.

  7. New users must download the supporting jar library files described below.

    Put these jars in the same directory that contains the jiggle.jar file.

    Do NOT unpack these jar files.

  8. Oracle JDBC drivers (check Oracle site for updates of jars, do not download ojdbc7.jar if your client host java is Java6):  (ojdbc7.jar) or  (ojdbc6.jar)

    OpenMap (Java 1.4):   (openmap.jar)

    QWClient map layer (Java 1.4):   (QWClient.jar)

    All of the above 1.4 jars in one zip:   (all-in-one14.zip). extract this zip archive into jiggle jar directory.

    Optional Swarm utility (Java 1.5):  (swarm-avo.zip) extract this zip archive into jiggle jar directory.

  9. Download supporting map data files

    Download and unzip map data files into jiggle jar directory from: (mapdata.zip)

    These map data files are referenced by some optional layers defined in the openmap.properties file The user can change the default locations when needed for a custom configuration.

  10. Define a user directory for Jiggle properties files.
  11. Define/create a directory for properties files and in the java command line set JIGGLE_USER_HOMEDIR to this path (paths containing spaces should be surrounded by quotes). Copy the application's .props, .properties files into this directory. Typical paths are a parallel directory to the application's jar files (e.g. ../props) or under the user's home directory root, for example:

  12. Download example properties files (properties.zip)

    Unzip the downloaded example properties files into your Jiggle user home directory (e.g. jiggle/props).

    By default the Jiggle application loads its user's properties from the file named jiggle.props, but an alternative filename can be specified as the first command line argument (%1, on windows, or $1 on unix).

    If the input command line named file (which defaults to jiggle.props when absent) does not exist, Jiggle will use default property values which can be saved to jiggle.props, or first, be reset using the GUI's 'Edit properties...' popup dialog and then saved. The only properties that a user must define are those that specify the local network id, database connection properties, hypoinverse location server properties, and waveserver properties. Additional setup/properties files used by the application are defined by property values in the main properties file, they are:

    For more information see additional properties file property definitions.

  13. Create a runtime script or bat file

  14. The script or .bat file is in the same directory as the jiggle.jar and contains a line of the form:

    java -Xms128M -Xmx512M -DgraphicsOption... -DJIGGLE_HOME=ProgramPath-DJIGGLE_USER_HOMEDIR=UserPropPath -jar jiggle.jar
    The -D command line options define system properties where ProgramPath is the directory containing the application's jar files and UserPropPath is the directory containing the properties files.

  15. Start the program

    Invoke the startup script from a command window or create a mouse click startup shortcut for the script on your desktop.

Example Jiggle screenshot
To Jiggle home page
To top of page