| Warning |
|---|
This article is just startingI am not entirely happy with the stop and start scripts and also not done picking apart the example provided by hsqldb and explaning the reasoning behind our own custom script. |
Starting
Script,
| Code Block |
|---|
|
#!/bin/bash
cd /opt/hsqldb
# Add date to nohup.out file which is automatically created by the nohup command to capture any output from commands sent to it
echo $(date) >nohup.out
# Assuming that java is the the class path.
# Execute Java program calling class path where -cp identifies classpath and,
# Creates a database file called BonsaiResourceBundleDatabase if it does not exist relative to the current directory
# -dbname.0 designates that the database will be called BonsaiResourceBundleDatabase
# Sends Java program to background and to not terminate via nohup command.
nohup java -cp lib/hsqldb.jar org.hsqldb.Server -database.0 file:data/BonsaiResourceBundleDatabase -dbname.0 BonsaiResourceBundleDatabase & |
| Warning |
|---|
For some reason the script requires the user to hit an extra return. I believe this is due to the nohup command. Investigate and resolve.
# Without this echo, the script will require that the user hit enter to return back to the command line
echo "hsqldb started" |
From the HSQLDB manual it provides this example,
| Code Block |
|---|
|
# Make an environment variable called CLASSPATH
export CLASSPATH
# Set CLASSPATH to include the hsqldb.jar file. Java will look at CLASSPATH list to know what to execute.
CLASSPATH=/path/to/hsqldb/lib/hsqldb.jar
# Executes Java program calling class and sends to background.
nohup java org.hsqldb.Server & |
Stopping
Script,
| Code Block |
|---|
|
cd /opt/hsqldb
java -jar lib/hsqldb.jar --sql "shutdown;" --rcFile ./sqltool.rc localhost-sa |
versus HSQLDB manual.
Resources
http://hsqldb.org/doc/2.0/guide/unix-chapt.html - start here and simplify these instructions.