Creating locations

Locations represent individual GraphDB servers, where the repository data is stored. They can be local (a directory on the disk) or remote (an end-point URL), and can be attached, edited and detached. Only a single location can be active at a time. Each location has a SYSTEM repository containing meta-data about how to initialise other repositories from the current location.

To manage your data locations:

  1. Start a browser and go to the Workbench web application using a URL of this form: http://localhost:7200. - substituting localhost and the 7200 port number as appropriate.
  2. Go to Setup -> Repositories.

Active location

When started, GraphDB creates GraphDB-HOME/data directory as an active location. To change the directory, see Configuring GraphDB Data Directory.


Change active location settings

Be default, the active location does not send anonymous usage statistics to Ontotext. To change this, click on the icon Change active location settings and enable it.


View or update its license

Click the Key icon


to check the details of your current license.

Inactive location

All inactive locations are listed below the active repository window. Here, you can change the locations settings, as well as disconnect the location from the running GraphDB.


Connect to a remote location

To connect to a remote location:

  1. Click the Connect to location button and add the HTTP RDF4J Location of your repository, for example http://localhost:8083.

  2. Optionally, you can set a user and a password for this location.

You can attach multiple locations but only one can be active at a given time. The active location is always shown in the navigation bar next to a plug icon.


Using basic HTTP authentication may be required for accessing the HTTP-JMX bridge in the Monitor views. Each GraphDB distribution contains a generated jolokia-secret in <graphdb-dist>/work/, when using remote location you should pass the jolokia-secret to access these features.


If you use the Workbench as a SPARQL endpoint, all your queries are sent to a repository in the currently active location. This works well if you do not change the active location. To have endpoints that are always accessible outside the Workbench, we recommend using standalone Workbench and Engine installations, connecting the Workbench to the Engine over a remote location and using the Engine endpoints (i.e., not the ones provided by the Workbench) in any software that executes SPARQL queries.

Configure a data location

Set the property in <graphdb_dist>/conf/ If no property is set, the default repositories location will be: <graphdb_dist>/data.