7.0 Portable HSQLDB

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

Introduction

Explain what HSQLDB is about.

Setup

To fill in, though it's pretty simple.

Starting

If the admin password has changed, the /opt/hsqldb/sqltool.rc must be edited.

The password in the sqltool.rc file is unencrpyted. This password MUST be encrypted.

Script,

#!/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 &

# 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,

# 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,

cd /opt/hsqldb
java -jar lib/hsqldb.jar --sql "shutdown;" --rcFile ./sqltool.rc localhost-sa

versus HSQLDB manual.

Backup

Start from really simple, using tar, to using script and then advanced using replication.

Changing Password

The syntax command for changing the password

SET PASSWORD password ;

Changes the password of the currently connected user. Empty password can be set using ""
In the ursis appication, the location that the properties file is inside a jar file located in
/opt/apache/tomcat/webapps/ursis/WEB-INF/lib/BrandingEngine.jar
Inside the BrandingEngine.jar is branding_config.properties, which sets the path of the properties file.
BrandingPropertiesLocation=/opt/apps/BrandingEngine/resources/T6/branding_env.properties

For the account that general users use, set the username and password in the branding_env.properties file.
The password encryption tool is in source control C:\SVN\tools\gtb-encryption\encryption.bat

Resources

http://hsqldb.org/doc/2.0/guide/unix-chapt.html - start here and simplify these instructions.

Page tree