This section is for users and system administrators that are unfamiliar with the GraphDB-Lite semantic repository software. The information contained in the following pages should be enough to get started with GraphDB-Lite, i.e. to install and configure the software, so that repository instances can be created and used.
GraphDB-Lite is packaged as a Storage and Inference Layer (SAIL) for the Sesame RDF framework. GraphDB-Lite can be used in two different ways:
The rest of this section gives detailed step by step instructions for installing and configuring Sesame and GraphDB-Lite, leading up to the creation of a GraphDB-Lite repository using the Sesame console (a command line script). For more information please check the "doc" folder of the GraphDB-Lite distribution zip file.
GraphDB will normally be built against the latest version of the Aduna OpenRDF Sesame framework. If using GraphDB with this version then the easiest way to deploy a GraphDB server instance is to copy the re-packaged Sesame Web applications (.war files) in to the Tomcat webapps directory. These can be found in the sesame_owlim directory in the GraphDB distribution ZIP file. These Web applications have been modified as follows:
After deployment, a GraphDB-Lite instance can be created using the workbench application as follows:
This longer install process should be used when a different or modified version of Sesame is being used. In this case, all the GraphDB-Lite files needs to be installed alongside Sesame in a step-by-step process as follows.
A suitable application server must be installed. The examples in this guide assume Apache Tomcat version 6.x is used. Importantly, the user must have sufficient privileges to write to the Tomcat webapps directory and to stop and start the Tomcat daemon.
No part of this guide is intended to supersede the documentation published with these 3rd party software components and the reader is strongly advised to familiarise himself/herself with these.
Assuming that an instance of Tomcat is available, the installation proceeds as follows:
Step by step (vanilla)
The status of the new repository can be checked using the Sesame workbench. Type the following URL in to a browser:
Step by step (Fedora linux)
Step by step (Windows)
When running on Fedora linux, Tomcat uses the following directories:
On a machine running Windows, Tomcat uses the following directories:
The Sesame framework is published as a zip file that is installed simply by unzipping it in to the target directory. This directory is called [SESAME_INSTALL] in this guide.
This directory is called [ADUNA_DATA] elsewhere in this guide. It can be overridden by setting a Java system property. When using Tomcat, this can be achieved by setting the JAVA_OPTS environment variable, for example (linux and Windows respectively):
export JAVA_OPTS='-Dinfo.aduna.platform.appdata.basedir=/other/dir/' set JAVA_OPTS=-Dinfo.aduna.platform.appdata.basedir=\other\dir\
Note that setting this environment variable must be done by the same user that runs the Tomcat server. This may not be the case when using 'sudo' to set up/start Tomcat, for instance when using port numbers below 1024, when it is necessary to run Tomcat with root privileges.
The Sesame server and workbench use SLF4J for logging, although they each map to different underlying logging implementations. The Sesame server has bindings to logback whereas the Sesame workbench has bindings to the Java Runtime logging framework. By default, the Sesame server logs to:
The default log level is INFO, but this can be adjusted after the first run by editing:
GraphDB also uses SLF4J for logging and the distribution includes the SLF4J-to-Java-logging mapping jar file. The repackaged openrdf-sesame war file that comes with GraphDB does not have this mapping, so in this case GraphDB logs as Sesame does to the logback framework.
Tomcat uses log4j and the logging details can set up by editing this file (on Linux):
or this file on Windows:
C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\logging.properties
By default, the Tomcat logs (on Linux) are written to:
and the logs (on Windows) are written to:
C:\Program Files\Apache Software Foundation\Tomcat 6.0\logs
Can not copy GraphDB-Lite jar file to the Sesame WEB-INF/lib directory.
This directory will not exist until the Sesame war files have been deployed to the [WEBAPPS] directory AND Tomcat is running. If the war files have been deployed, but the directory does not exist, try restarting Tomcat.
Can not connect the Sesame console to the local Sesame server at http://localhost:8080/openrdf-sesame
Make sure that the Sesame war files have been deployed and that Tomcat is running. Restart Tomcat if necessary.
Can not create a GraphDB-Lite repository using the Sesame console
Make sure that the repository template file [GraphDBLITE]/templates/swiftowlim.ttl has been copied to the 'templates' sub-directory of the Sesame console's data directory.
Can not create a GraphDB-Lite repository, the Sesame console says unknown Sail type – owlim:Sail
The Sesame console can not find the GraphDB-Lite jar file. Make sure it was copied from [GraphDBLITE]/lib to the Sesame installation folder here: [SESAME]/lib
Cannot use my custom rule file (pie file), an exception occurred
Custom rule files require the use of a Java Development Kit (JDK) version 1.6 or higher, due to the mechanism used to locate the Java compiler. Furthermore, the application (application server) must be started with the Java Virtual Machine (JVM) that comes with this JDK.
A repository can be created using the openrdf console, but any operation using this repository results in a long error message
Make sure that the GraphDB jar file has been copied to the Sesame Web application's WEB-INF/lib directory.
Sesame Workbench starts, but gives memory error on the 'explore' and 'query' menus
The maximum heap space must be increased, i.e. Tomcat's Java virtual machine must be allowed to allocate more memory. This can be done by setting the environment variable 'CATALINA_OPTS' to include the desired value, e.g. -Xmx1024m.
GraphDB-Lite Installation Guide
Skip to end of metadata Go to start of metadata