Summary of what you need to run Jiggle:

• A reasonably fast processor and at least 2G of memory
• The Java Run-Time Environment (JRE)
• Application and supporting  jar  files
• Program properties files
• Script to start program (you can create a desktop shortcut to invoke it).
• Oracle database having NCEDC schema tables,  JASI views and the required PL/SQL packages.

1. Create a valid Java runtime environment on your computer.
   
   
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


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


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.


3. Download the appropriate jiggle jar file and put it in the application directory created above.




Do NOT unpack the jar file.
The "test" version is the latest code build. Whatever version you download, you should rename it to match your startup (script) command reference jar filename.


 Latest Version Release Notes


Java 1.5 compilation (requires swarm-avo.zip extracted into jiggle application directory):
Below version also requires update of ORIGIN table RFLAG constraint:


 jiggleTestUTC15I.jar (2009-11-20)


Java 1.6 compilation (requires swarm-avo.zip extracted into jiggle application directory):
Below version also requires update of ORIGIN table RFLAG constraint:


 jiggleTestUTC16I.jar (2009-11-20)



4. Download supporting class library files.
   
   Download the following .jar files and put them in the same directory that contains the jiggle.jar file.
   If you have already downloaded these files, you do not need to download them again.

Do NOT unpack these .jar files.

Oracle JDBC drivers (Java 1.4):  Download   (ojdbc14.jar)
    NOTE: using jdbc:oci subprotocol with dbaseTNSname alias requires an Oracle client installation,  See Oracle Instant Client instructions

OpenMap (Java 1.4):  Download   (openmap.jar)

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

GIF image handler (Java 1.4):  Download   (acme.jar)

All of the above supporting 1.4 jars in one zip:  Download   (all-in-one14.zip). You must extract the zip archive files into the jiggle jar directory.

Optional Swarm utility in Jiggle (requires Java runtime version 5 or higher):

Swarm utility (Java 1.5) (Alaska Volcano Observatory). Download  (swarm-avo.zip)
You must extract the zip archive files into the jiggle jar directory.

5. Download supporting map data files
   

   Download and unzip map data files into the 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.

6. Define a user directory for Jiggle properties files.
   

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:

• WindowsXP "C:\Program Files\Jiggle\props" or %USERPROFILE% (e.g. "C:\Documents and Settings\Kate\jiggle")
• UNIX /usr/Jiggle/props or $HOME (e.g. /home/Kate/jiggle)


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

   • eventSelection.props contains properties defining the event catalog selection filter settings.
     
   • openmap.properties properties defining map setup and layers that can be added, removed, or modified.
     
   • xxMagEng.props contains properties defining magnitude engine setup for a magnitude type xx (e.g. ml, md).
     
   • xxMagMeth.props contains properties defining magnitude method setup for a magnitude type xx (e.g. ml, md).
     
   • xchannelList.cache a serialized object binary file that is created in your .jiggle user home directory after the application startup containing channel data that was returned from a query of the database. This file is read into a Java the next time the program is started to avoid the long time wait needed to process the database query.
     
   • openmap.properties contains map configuration properties that reference map data files which, by default, are located in the mapdata subdirectory tree below the JIGGLE_HOME (jar file) directory.
     
   
   For more information see additional properties file property definitions.
   
   
8. Create a runtime script or bat file



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.


• A UNIX executable script would contains a line like:

java -Xmx512M -DJIGGLE_HOME=/usr/jiggle -DJIGGLE_USER_HOMEDIR=$HOME/jiggle -jar jiggle.jar $1


• The Mac OSX setup is the same as the UNIX setup (on a Mac $HOME is /Users/your_user_name).
  java -Xmx512M -DJIGGLE_HOME=/usr/jiggle -DJIGGLE_USER_HOMEDIR=$HOME/jiggle -jar jiggle.jar $1
  
  Put the command line in a file called jiggle.command and from a terminal window make it executable:
  chmod +x jiggle.command
  
  
• A Windows .bat file would contain a line like:
  
java -Xmx512M -DgraphicsOption... DJIGGLE_HOME="%PROGRAMFILES%\Jiggle" -DJIGGLE_USER_HOMEDIR="%USERPROFILE%\jiggle" -jar jiggle.jar %1

NOTE: On Windows to prevent crashes (BSOD) user MUST added 2 graphics options to command line that disable the MS DirectDraw acceleration. These 2 options are:


-Dsun.java2d.ddoffscreen=false -Dsun.java2d.d3d=false



9. Start the program

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