1 # $Id: hsqldb-1.73.0-standard.cfg,v 1.1 2004/12/23 22:21:08 fnasser Exp $
3 # Sample configuration file for HSQLDB database server.
4 # See the "UNIX Quick Start" chapter of the Hsqldb User Guide.
6 # N.b.!!!! You must place this in the right location for your type of UNIX.
7 # See the init script "hsqldb" to see where this must be placed and
8 # what it should be renamed to.
10 # This file is "sourced" by a Bourne shell, so use Bourne shell syntax.
12 # This file WILL NOT WORK until you set (at least) the non-commented
13 # variables to the appropriate values for your system.
14 # Life will be easier if you avoid all filepaths with spaces or any other
15 # funny characters. Don't ask for support if you ignore this advice.
17 # Thanks to Meikel Bisping for his contributions. -- Blaine
19 # JPackage hsqldb home is /var/lib/hsqldb
21 HSQLDB_HOME=/var/lib/hsqldb
23 # JPackage source Java config
27 JAVA_EXECUTABLE=${JAVA_HOME}/bin/java
29 # Unless you copied a hsqldb.jar file from another system, this typically
30 # resides at $HSQLDB_HOME/lib/hsqldb.jar, where $HSQLDB_HOME is your HSQLDB
31 # software base directory.
32 HSQLDB_JAR_PATH=${HSQLDB_HOME}/lib/hsqldb.jar
34 # Where the file "server.properties" (or "webserver.properties") resides.
35 SERVER_HOME=${HSQLDB_HOME}
37 # What UNIX user the Server/WebServer process will run as.
38 # (The shutdown client is always run as root or the invoker of the init script).
39 # Runs as root by default, but you should take the time to set database file
40 # ownerships to another user and set that user name here.
41 # You do need to run as root if your Server/WebServer will run on a privileged
43 # If you really do want to run as root, comment out the HSQLDB_OWNER setting
44 # completely. I.e., do not set it to root. This will run Server/Webserver
45 # without any "su" at all.
48 # We require all Server/WebServer instances to be accessible within
49 # $MAX_START_SECS from when the Server/WebServer is started.
51 # Raise this is you are running lots of DB instances or have a slow server.
56 # Time to allow for JVM to die after all HSQLDB instances stopped.
60 # These are "urlid" values from a SqlTool authentication file
61 # ** IN ADDITION TO THOSE IN YOUR server.properties OR webserver.properties **
62 # file. All server.urlid.X values from your properties file will automatically
63 # be started/stopped/tested. $SHUTDOWN_URLIDS is for additional urlids which
64 # will stopped. (Therefore, most users will not set this at all).
65 # Separate multiple values with white space. NO OTHER SPECIAL CHARACTERS!
66 # Make sure to quote the entire value if it contains white space separator(s).
67 # Defaults to none (i.e., only urlids set in properties file will be stopped).
68 #SHUTDOWN_URLIDS='sa mygms'
70 # SqlTool authentication file used only for shutdown.
71 # The default value will be sqltool.rc in root's home directory, since it is
72 # root who runs the init script.
73 # (See the SqlTool chapter of the HSQLDB User Guide if you don't understand
75 AUTH_FILE=${HSQLDB_HOME}/sqltool.rc
77 # Set to 'WebServer' to start a HSQLDB WebServer instead of a Server.
78 # Defaults to 'Server'.
79 #TARGET_CLASS=WebServer
81 # Server-side classpath IN ADDITION TO the HSQLDB_JAR_PATH set above.
82 # The classpath here is *earlier* than HSQLDB_JAR_PATH, to allow you
83 # override classes in the HSQLDB_JAR_PATH jar file.
84 # In particular, you will want to add classpath elements to give access of
85 # all of your store procedures (store procedures are documented in the
86 # HSQLDB User Guide in the SQL Syntax chapter.
89 # If you're adding files to the classpath in order to be able to call them
90 # from SQL queries, you will be unable to access them unless you adjust the
91 # value of the system property hsqldb.method_class_names. Please see the
92 # comments on SERVER_JVMARGS, at the end of this file.
93 # SERVER_ADDL_CLASSPATH=/home/blaine/storedprocs.jar:/usr/dev/dbutil/classes
95 # For TLS encryption for your Server, set these two variables.
96 # N.b.: If you set these, then make this file unreadable to non-root users!!!!
97 # See the TLS chapter of the HSQLDB User Guide, paying attention to the
98 # security warning(s).
99 # If you are running with a private server cert, then you will also need to
100 # set "truststore" in the your SqlTool config file (location is set by the
101 # AUTH_FILE variable in this file, or it must be at the default location for
103 #TLS_KEYSTORE=/path/to/jks/server.store
104 #TLS_PASSWORD=password
106 # Any JVM args for the invocation of the JDBC client used to verify DB
107 # instances and to shut them down (SqlToolSprayer).
108 # For multiple args, put quotes around entire value.
109 #CLIENT_JVMARGS=-Djavax.net.debug=ssl
111 # Any JVM args for the server.
112 # For multiple args, put quotes around entire value.
115 # The default value of SERVER_JVMARGS sets the system property
116 # hsqldb.method_class_names to be empty. This is in order to lessen the
117 # security risk posed by HSQLDB allowing Java method calls in SQL statements.
118 # The implications of changing this value (as explained by the authors of
119 # HSQLDB) are as follows:
120 # If [it] is not set, then static methods of all available Java classes
121 # can be accessed as functions in HSQLDB. If the property is set, then
122 # only the list of semicolon separated method names becomes accessible.
123 # An empty property value means no class is accessible.
124 # Regardless of the value of hsqldb.method_class_names, methods in
125 # org.hsqldb.Library will be accessible.
126 # Before making changes to the value below, please be advised of the possible
127 # dangers involved in allowing SQL queries to contain Java method calls.
128 SERVER_JVMARGS=-Dhsqldb.method_class_names=\"\"