z2-Environment

h2. Running a Java DB Network Server

In samples we use the Java DB, i.e. the SQL database implementation that comes with the Java SE Development Kit (JDK) by Oracle (except for Mac OS in which case you have to use Apache Derby). Java DB is the same as the "Apache Derby DB":http://db.apache.org/derby - see also the "installation how-to":http://db.apache.org/derby/papers/DerbyTut/install_software.html.

The instructions below apply to both, there is only a difference in the installation path. 

For general information on Java DB go to http://docs.oracle.com/javadb/10.8.2.2/getstart/index.html

To run the Java DB in server mode, which is what we want to do, run

<pre><code class="ruby">

mkdir derby

cd derby

java -jar $JAVA_HOME/db/lib/derbyrun.jar server start

</code></pre>

assuming you want to run it in the folder *derby*. At a second time you can omit the "mkdir" command of course. The environment variable JAVA_HOME is expected to point to your JDK installation folder. When you installed Apache Derby and followed the instructions mentioned above, you have to replace $JAVA_HOME by $DERBY_HOME.

On Windows run

<pre><code class="ruby">

mkdir derby

cd derby

java -jar %JAVA_HOME%\db\lib\derbyrun.jar server start

</code></pre>

In order to interactively query Java DB, we recommand to use the Data Source Explorer view in Eclipse. But any SQL client that can make use of JDBC drivers should be fine. The driver for Java DB can be found (at the time of this writing) in *$JAVA_HOME/db/lib/derbyclient.jar* (and similarly on Windows).