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 endpoint URL), and can be attached, edited, and detached. Only a single location can be active at a time.

To manage your data locations:

  1. Start a browser and go to the Workbench web application using a URL of the form http://localhost:7200, substituting localhost and the 7200 port number as appropriate.

  2. Go to Setup ‣ Repositories.

Active location

Upon startup, GraphDB creates GraphDB-HOME/data directory as an active location. To change the directory, see Configuring GraphDB data directory.

_images/Repository_locations.png

Change active location settings

By default, the active location does not send anonymous usage statistics to Ontotext. To change this, click on the icon Edit common settings for these repositories and enable it.

_images/usage-statistics-icon.png

The following settings dialog will appear:

_images/usage-statistics.png

View or update active location license

Click the key icon

_images/view-license-icon.png

to check the details of your current license.

_images/view-license.png

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.

_images/inactive-locations.png

Connect to a remote location

To connect to a remote location:

  1. Click the Attach remote location button and and enter the URL of the remote GraphDB instance, for example http://localhost:7300.

  2. In terms of authentication methods to the remote location, GraphDB offers three options:

    1. None: The security of the remote location is disabled, and no authentication is needed.

      _images/attach-location-auth-none.png

    2. Basic authentication: The security of the remote location has basic authentication enabled (default setting). Requires a username and a password.

      _images/attach-location-auth-basic.png

    3. Signature: Uses the token secret, which must be the same on both GraphDB instances. For more information on configuring the token secret, see the GDB authentication section of the Access Control documentation.

      _images/attach-location-auth-signature.png

      Hint

      Signature authentication is the recommended method for a cluster environment, as both require the same authentication settings.

Note

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.

Note

You can connect to a remote location over HTTPS as well. To do so:

  1. Enable HTTPS on the remote host.

  2. Set the correct Location URL, for example https://localhost:8083.

  3. In case the certificate of the remote host is self-signed, you should add it to you JVM’s SSL TrustStore.

Configure a data location

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