The qsac service is distributed in two forms. The first is a
qsac-n.n.war file, which can be dropped into a Tomcat
installation, the second is a qsac-standalone-n.n.jar
file (implemented using
Jetty), which can be run to start
a standalone server.
You can find both of these on the SKUA download page at googlecode.
You will need to use Java 6 to run Quaestor.
Qsac is distributed as a .war file and as a
standalone web server.
To install the .war file, download that and install it in
your Tomcat server in the usual way.
You can configure the server by adjusting the unpacked
.war file's WEB-INF/web.xml. Most of the
<init-param> parameters should be left alone, but
you may well need to change the persistence-directory
setting. This indicates where qsac should persist knowledgebases (if
that functionality is enabled, at compile time, which is usually is).
The default value, which places the persistence directory within the
Tomcat server's work/ directory, probably isn't the best
location for a production server but should be harmless as a default.
To start up the standalone server, download the
qsac-standalone-n.n.jar file (of a suitable version
number), and either double-click it (if that's appropriate for your
OS), or start it with a command like:
% java -jar qsac-standalone-n.n.jar
You can give a trailing --port=nnnn option to change
the port on which the server listens, from the default 8080. Go to
http://localhost:8080 to see the top of the SAC service
(or whatever you have chosen the port to be).
As with the .war file, there is very little to
configure in the standalone server. To change the location of the
persistence directory, give a value for the
persistence-directory property when you start the server,
by giving the -Dpersistence-directory=/path option to the
java command. The default places the persistence
directory in the current working directory.