Chapter 5. Server software installation

Table of Contents

5.1. Required software
5.2. Sesame Server and Workbench installation
5.3. Logging Configuration
5.4. Repository Configuration

In this section, we explain how you can install a Sesame HTTP Server. You can skip this if you are not planning to run a Sesame server but intend to use Sesame as a library to program against.

5.1. Required software

The Sesame server software requires the following software:

  • Java 5 or newer
  • A Java Servlet Container that supports Java Servlet API 2.4 and Java Server Pages (JSP) 2.0, or newer. We recommend using a recent, stable version of Apache Tomcat. At the time of writing, this is either version 5.5.x or 6.x.

5.2. Sesame Server and Workbench installation

The Sesame 2 server software comes in the form of two Java Web Applications: OpenRDF Sesame Server and OpenRDF Workbench.

Sesame Server provides HTTP access to Sesame repositories and is meant to be accessed by other applications. Apart from some functionality to view the server's log messages, it doesn't provide any user oriented functionality. Instead, the user oriented functionality is part of OpenRDF Workbench. OpenRDF Workbench provides a web interface for querying, updating and exploring the repositories of a Sesame Server.

If you have not done so already, you will first need to download the Sesame 2 SDK. Both Sesame Server and OpenRDF Workbench can be found in the war directory of the SDK. The war-files in this directory need to be deployed in a Java Servlet Container (see Section 5.1, “Required software”). The deployment process is container-specific, please consult the documentation for your container on how to deploy a web application.

After you have deployed the Sesame Server webapp, you should be able to access it, by default, at path /openrdf-sesame. You can point your browser at this location to verify that the deployment succeeded[1]. Your browser should show the Sesame welcome screen as well as some options to view the server logs, among other things. Similarly, after deployment, the OpenRDF Workbench should be available at path /openrdf-workbench.

5.3. Logging Configuration

Both Sesame Server and OpenRDF Workbench use the Logback logging framework. In its default configuration, all Sesame Server log messages are sent to the log file [ADUNA_DATA]/OpenRDF Sesame/logs/main.log (and log messages for the Workbench to the same file in [ADUNA_DATA]/OpenRDF workbench). See Chapter 7, Application directory configuration for more info about data directories.

The default log level is INFO, indicating that only important status messages, warnings and errors are logged. The log level and -behaviour can be adjusted by modifying the [ADUNA_DATA]/OpenRDF Sesame/conf/logback.xml file. This file will be generated when the server is first run. Please consult the logback manual for configuration instructions.

5.4. Repository Configuration

A clean installation of a Sesame Server has a single repository by default: the SYSTEM repository. This SYSTEM repository contains all configuration data for the server, including data on which other repositories exists and (in future releases) the access rights on these repositories. This SYSTEM repository should not be used to store data that is not related to the server configuration.

The best way to create and manage repositories in a SYSTEM repository is to use the Sesame Console or OpenRDF Workbench. The Sesame Console is a command-line application for interacting with Sesame, see Chapter 6, Sesame Console.

[1] There is a known issue (SES-845) with deployment of the Sesame Server in Apache Tomcat version 7, where this link does not redirect to the correct location as expected. If you are running Sesameo on Tomcat 7, try accessing /openrdf-sesame/home/overview.view instead