Running Fuseki with UI

Fuseki/UI can be run in a number of ways:

Fuseki is also packaged as a plain server “Fuseki Main” with no UI for use as a configurable SPARQL server, for building as a Docker container, and as a deployment and development standalone server.

Both packaging used the same configuration file format, and in standalone server mode, the same command line arguments.

See “Fuseki Configuration” for information on how to provide datasets and configure services using the configuration file.

Fuseki as a Standalone Server

This is running Fuseki from the command line.

To publish at http://host:3030/NAME:

where /NAME is the dataset publishing name at this server in URI space.

TDB1 database:

fuseki-server [--loc=DIR] [[--update] /NAME]

The argument --tdb2 puts the command line handling into “TDB2 mode”. A dataset created with --loc is a TDB2 dataset. TDB2 database:

fuseki-server --tdb2 [--loc=DIR] [[--update] /NAME]

In-memory, non-peristent database (always updatable):

fuseki-server --mem /NAME

Load a file at start and provide it read-only:

fuseki-server --file=MyData.ttl /NAME

where “MyData.ttl” can be any RDF format, both triples or quads.

Administrative functions are only available from “localhost”.

See fuseki-server --help for details of more arguments.


When run from the command line, the server creates its work area in the directory named by environment variable FUSEKI_BASE. When run from the command line, this defaults to the current directory.

Fuseki layout

If you get the error message Can't find jarfile to run then you either need to put a copy of fuseki-server.jar in the current directory or set the environment variable FUSEKI_HOME to point to an unpacked Fuseki distribution.

Starting with no dataset and no configuration is possible. Datasets can be added from the admin UI to a running server.

Fuseki as a Service

Fuseki can run as an operating system service, started when the server machine boots. The script fuseki is a Linux init.d with the common secondary arguments of start and stop.

Process arguments are read from /etc/default/fuseki including FUSEKI_HOME and FUSEKI_BASE. FUSEKI_HOME should be the directory where the distribution was unpacked.

Fuseki as a Web Application

Fuseki can run from a WAR file. Fuseki requires at least support for the Servlet 3.0 API (e.g. Apache Tomcat 7 or Jetty 8) as well as Java8.

FUSEKI_HOME is not applicable.

FUSEKI_BASE defaults to /etc/fuseki which must be a writeable directory. It is initialised the first time Fuseki runs, including a Apache Shiro security file but this is only intended as a starting point. It restricts use of the admin UI to the local machine.