This section is for users and system administrators that are unfamiliar with the SwiftOWLIM semantic repository software. The information contained in the following pages should be enough to get started with SwiftOWLIM, i.e. to install and configure the software so that repository instances can be created and used.
SwiftOWLIM is packaged as a Storage and Inference Layer (SAIL) for the Sesame RDF framework . SwiftOWLIM can be used in two different ways: One approach is to integrate it in an application using it as a library. An example of doing this is given in the 'getting-started' folder of the SwiftOWLIM distribution zip file. Users intending to use SwiftOWLIM in this way do not need to install the Sesame Web applications (Server and Workbench) and must only set a few environment variables as detailed in the SwiftOWLIM user guide in the section covering the getting-started example application.
This guide covers the installation of SwiftOWLIM . Required software for this comprises:
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.
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.
Assuming that an instance of Tomcat is available, the installation proceeds as follows:
* Copy the SLJ4J logger libraries from the Sesame Server to the Sesame Workbench application, i.e. from [WEBAPPS]/openrdf-sesame/WEB-INF/lib/logback-* to [WEBAPPS]/openrdf-workbench/WEB-INF/lib
The status of the new repository can be checked using the Sesame workbench. Type the following URL in to a browser:
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):
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 logback for logging. The Sesame server logs to:
And the Workbench logs to:
The default log level is INFO, but this can be adjusted after the first run by editing:
There is a note in the Sesame documentation that the simple logging framework for java (slf4j) is used, which implies that a bridge jar for the logging framework OWLIM uses is also required, e.g. SLF4J-to-log4j.jar
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.
Make sure that the repository template file [SWIFTOWLIM]/templates/swiftowlim.ttl has been copied to the 'templates' subdirectory of the Sesame console's data directory.
The Sesame console can not find the SwiftOWLIM jar file. Make sure it was copied from [SWIFTOWLIM]/lib to the Sesame installation folder here: [SESAME]/lib
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 both the OWLIM and the separate TRREE jar files have been copied to the Sesame Web application's WEB-INF/lib directory. If only the OWLIM jar is copied, then this is enough to create a repository, but the repository cannot be used without the TRREE jar file.
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
Skip to end of metadata Go to start of metadata