GraphDB-Lite Usage Scenarios

compared with
Current by Gergana Petkova
on Sep 18, 2014 12:49.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History

GraphDB is packaged as a Storage and Inference Layer (SAIL) for [Sesame version 2.x|] and makes extensive use of the features and infrastructure of Sesame, especially the RDF model, RDF parsers and query engines. Explicit and inferred statements are stored in highly-optimized data structures. The inferred closure is updated through inference at the end of each transaction that modifies the repository.
GraphDB implements the Sesame SAIL interface so that it can be integrated with the rest of the Sesame framework, e.g. the query engines and the web user interface tools. A typical user application uses GraphDB directly through the Sesame SAIL API. When an a GraphDB repository is exposed employing the Sesame HTTP Server, users can manage the repository through the Sesame Workbench Web application, or with other tools that can integrate with Sesame, e.g. ontology editors like TopBraid Composer.
Sesame comprises a large collection of libraries, utilities and APIs, but the important components for this section are:
* the Sesame classes and interfaces (API) that provide uniform access to SAIL components from multiple vendors/publishers;
h1. Managing repositories with the Sesame Workbench

The [installation section|GraphDB-Lite Installation] explains how to set up an a GraphDB repository that is exposed via the Sesame HTTP Server. In summary, the Sesame Server and Workbench applications are deployed to a Tomcat instance. After this, the workbench can be used to connect to the Sesame server and create a repository instance.
When the Sesame server is running, it will show a welcome message at the following URL: