• Topic
  • Discussion
  • VOS.VirtSesame2HttpRepository(Last) -- DAVWikiAdmin? , 2017-06-13 05:39:55 Edit WebDAV System Administrator 2017-06-13 01:39:55

    Virtuoso RDF4J and Sesame HTTP Repository Configuration and Usage

    What

    Eclipse RDF4J (formerly known as OpenRDF Sesame) is an open source Java framework for storing, querying and reasoning with RDF and RDF Schema. It can be used as a database for RDF and RDF Schema, or as a Java library for applications that need to work with RDF internally. The RDF4J HTTP and Console repositories serves as a proxy for a RDF store hosted on a remote RDF4J server, enabling the querying of the RDF store using the RDF4J HTTP protocol.

    Why

    The RDF4J HTTP repository endpoint provides users with the greater flexibility for manipulating the RDF store via a common interface. RDF4J provides you with the necessary tools to parse, interpret, query and store all this information, embedded in your own application if you want, or, if you prefer, in a separate database or even on a remote server.

    How

    To create a new RDF4J HTTP repository, the Console needs to create such an RDF document and submit it to the SYSTEM repository. The Console uses so called repository configuration templates to accomplish this. Repository configuration templates are simple Turtle RDF files that describe a repository configuration, where some of the parameters are replaced with variables. The Console parses these templates and asks the user to supply values for the variables. The variables are then substituted with the specified values, which produces the required configuration data. Refer to the RDF4J Server, Workbench, and Console documentation for more details on it usage.

    Setup and Testing

    This section details the steps required for configuring and testing a Virtuoso RDF4J or Sesame Repository, both using the HTTP and Console RDF4J or Sesame repositories.

    Requirements

    Setup RDF4J or Sesame HTTP Repository

    This section details the steps required for configuring and testing a Virtuoso HTTP RDF4J or Sesame Repository.

    1. Install Apache Tomcat web server
    2. If using RDF4J:
      • From the RDF4J 2.x SDK "lib" directory copy the "rdf4j-server.war" and "rdf4j-workbench.war" files to the tomcat "webapps" directory where they will automatically be deployed creating two new sub directories "rdf4j-server" and "rdf4j-workbench".
      • Place the corresponding Virtuoso RDF4J 2.x Provider "virt_rdf4j.jar" and JDBC Driver "virtjdbc4_2.jar" into the Tomcat ~/webapps/rdf4j-server/WEB-INF/lib/ and ~/webapps/rdf4j-workbench/WEB-INF/lib/ directories for use by the RDF4J HTTP Repository for accessing the Virtuoso RDF repository.
      • Place the "create.xsl" and "create-virtuoso.xsl" files in the Tomcat ~/webapps/rdf4j-workbench/transformations/ directory. Note "create.xsl" replaces the default provided with RDF4J and contains the necessary entries required to reference the new "create-virtuoso.xsl" template file for Virtuoso repository configuration.
      • The RDF4J HTTP Repository will now be accessible on the URLs
    3. If using Sesame:
      • From Sesame 2.3.1 or higher "lib" directory copy the "openrdf-sesame.war" and "openrdf-workbench.war" files to the tomcat "webapps" directory where they will automatically be deployed creating two new sub directories "openrdf-sesame" and "openrdf-workbench".
      • Place the corresponding Virtuoso Sesame Provider "virt_sesame2.jar" or "virt_sesame4.jar" and JDBC Driver "virtjdbc4.jar" into the Tomcat ~/webapps/openrdf-sesame/WEB-INF/lib/ and ~/webapps/openrdf-workbench/WEB-INF/lib/ directories for use by the Sesame HTTP Repository for accessing the Virtuoso RDF repository.
      • Place the "create.xsl" and "create-virtuoso.xsl" files in the Tomcat ~/webapps/openrdf-workbench/transformations/ directory. Note "create.xsl" replaces the default provided with Sesame and contains the necessary entries required to reference the new "create-virtuoso.xsl" template file for Virtuoso repository configuration.
      • The Sesame HTTP Repository will now be accessible on the URLs

        http://localhost:8080/openrdf-sesame http://localhost:8080/openrdf-workbench

    4. The Eclipse RDF4J or Sesame OpenRDF Workbench is used for accessing the RDF4J or Sesame HTTP Repositories, loading "http://localhost:8080/openrdf-workbench" will enable the default "SYSTEM" repository to be accessed.
      • RDF4J



      • Sesame



    5. Click on the "New Repository" link in the left frame to create a new RDF4J or Sesame Repository.
      • RDF4J



      • Sesame



    6. Select the "Virtuoso RDF Store" from the "Type" drop down list box presented.
      • RDF4J



      • Sesame



    7. Choose suitable repository "ID" and "Title" for the Virtuoso repository to be created and click "Next".
      • RDF4J



      • Sesame



    8. Fill in the connection parameters for the target Virtuoso sever the repository is to be created for and click the "create" button. The minimum required are the hostname, port number, username and password of the Virtuoso Server.
      • RDF4J



      • Sesame



    9. The new Virtuoso respository will be created and its summary page displayed.
      • RDF4J



      • Sesame



    10. Click on the "Namespaces" link in the left frame to obtain a list of the available namespaces in the Virtuoso repository.
      • RDF4J



      • Sesame



    11. Click on the "Context" link in the left frame to obtain a list of the available contexts in the Virtuoso repository.
      • RDF4J



      • Sesame



    12. Click on the "Types" link in the left frame to obtain a list of the available types in the Virtuoso repository.
      • RDF4J



      • Sesame



    13. Click on the "Query" link in the left frame, enter a suitable SPARQL query to execute against the Virtuoso repository and click the "execute" button.
      • RDF4J



      • Sesame



    14. The results of the SPARQL query are returned.
      • RDF4J



      • Sesame



    15. Click on the "SPARQL Update" link in the left where SPARQL update queries can be executed against the Virtuoso repository and click the "execute" button.
      • RDF4J



    16. Click on the "Repositories" link in the left frame and the newly created Virtuoso repository entry is displayed along side the default SYSTEM repository.
      • RDF4J



      • Sesame


    Setup RDF4J or Sesame Console Repository

    This section details the steps required for configuring and testing a Virtuoso RDF4J Console Repository

    1. Extract RDF4J 2.x SDK or Sesame 2.3.1 or higher archive to a location of choice and place the virt_rdf4j.jar, virt_sesame2.jar or virt_sesame4.jar and virtjdbc4.jar files to the sesame "lib" directory
    2. Start the RDF4J or Sesame console application by running the "console.bat" script in the sesame "bin" directory and then "exit." the program

      $ sh console.sh SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/logback-classic-0.9.18.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/slf4j-jdk14-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 10:32:38.317 [main] DEBUG info.aduna.platform.PlatformFactory - os.name <http://os.name> <http://os.name> = mac os x 10:32:38.351 [main] DEBUG info.aduna.platform.PlatformFactory - Detected Mac OS X platform Connected to default data directory Commands end with '.' at the end of a line Type 'help.' for help exit.

    3. This will create the necessary sesame application data directories as detailed in the RDF4J or Sesame data directory configuration documentation.

      Windows - C:\Documents and Settings\LocalService\Application Data\Aduna\ Mac OS X - /Users/myuser/Library/Application Support/Aduna/ Linux - $HOME/.aduna/

    4. If you do not want to use the default sesame data directory location the RDF4J or Sesame console application can be started by specifying a custom data directory location with the "-d" option. Note in this case the directory "OpenRDF Sesame console" always has to be manually appended to the directory as RDF4J/Sesame assumes the data file will reside in a sub directory of this name.

      $ sh console.sh -d /Users/myuser/OpenRDF Sesame console

    5. Add the virtuoso.ttl file to the ~/OpenRDF Sesame console/templates folder, to enable the Virtuoso repository default configuration parameters to be located.
    6. Start the sesame console application with the required data directory location and create a Virtuoso repository as detailed in the steps below, the key parameters to be specified being the target Virtuoso server hostname, port number, username, password and a unique "Repository ID".

      $ sh console.sh SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/logback-classic-0.9.18.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/slf4j-jdk14-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 10:32:38.317 [main] DEBUG info.aduna.platform.PlatformFactory - os.name <http://os.name> <http://os.name> = mac os x 10:32:38.351 [main] DEBUG info.aduna.platform.PlatformFactory - Detected Mac OS X platform Connected to default data directory Commands end with '.' at the end of a line Type 'help.' for help create virtuoso . Please specify values for the following variables: Host list [localhost:1111]: Username [dba]: Password [dba]: Default graph name [sesame:nil]: Enable using batch optimization (false|true) [false]: Use RoundRobin for connection (false|true) [false]: Buffer fetch size [200]: Inference RuleSet name [null]: Repository ID [virtuoso]: myvirt Repository title [Virtuoso repository]: Repository created show r . +---------- |SYSTEM |myvirt ("Virtuoso repository") +---------- open myvirt . Opened repository 'myvirt' myvirt> show n . +---------- |bif bif: |dawgt http://www.w3.org/2001/sw/DataAccess/tests/test-dawg# |dbpedia http://dbpedia.org/resource/ |dbpprop http://dbpedia.org/property/ |dc http://purl.org/dc/elements/1.1/ |foaf http://xmlns.com/foaf/0.1/ |geo http://www.w3.org/2003/01/geo/wgs84_pos# |go http://purl.org/obo/owl/GO# |math http://www.w3.org/2000/10/swap/math# |mesh http://purl.org/commons/record/mesh/ |mf http://www.w3.org/2001/sw/DataAccess/tests/test-manifest# |nci http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl# |obo http://www.geneontology.org/formats/oboInOwl# |owl http://www.w3.org/2002/07/owl# |protseq http://purl.org/science/protein/bysequence/ |rdf http://www.w3.org/1999/02/22-rdf-syntax-ns# |rdfdf http://www.openlinksw.com/virtrdf-data-formats# |rdfs http://www.w3.org/2000/01/rdf-schema# |sc http://purl.org/science/owl/sciencecommons/ |scovo http://purl.org/NET/scovo# |skos http://www.w3.org/2004/02/skos/core# |sql sql: |vcard http://www.w3.org/2001/vcard-rdf/3.0# |virtrdf http://www.openlinksw.com/schemas/virtrdf# |void http://rdfs.org/ns/void# |xf http://www.w3.org/2004/07/xpath-functions |xml http://www.w3.org/XML/1998/namespace |xsd http://www.w3.org/2001/XMLSchema# |xsl10 http://www.w3.org/XSL/Transform/1.0 |xsl1999 http://www.w3.org/1999/XSL/Transform |xslwd http://www.w3.org/TR/WD-xsl |yago http://dbpedia.org/class/yago/ +---------- exit.

    Connection to RDF4J or Sesame HTTP repository from Console repository

    The RDF4J or Sesame Console repository can connect to a RDF4J or Sesame HTTP repository and vice-versa, enabling access to remote RDF4J or Sesame HTTP repositories from a local server.

    1. The RDF4J or Sesame Console repository can connect to a RDF4J or Sesame HTTP repository and query it as if local using the "connect" command.

      $ sh console.sh SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/logback-classic-0.9.18.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/Users/myuser/openrdf-sesame-2.3.1/lib/slf4j-jdk14-1.5.10.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 10:32:38.317 [main] DEBUG info.aduna.platform.PlatformFactory - os.name <http://os.name> <http://os.name> = mac os x 10:32:38.351 [main] DEBUG info.aduna.platform.PlatformFactory - Detected Mac OS X platform Connected to default data directory Commands end with '.' at the end of a line Type 'help.' for help > connect http://localhost:8080/openrdf-sesame. Connected to http://localhost:8080/openrdf-sesame > show r. +---------- |SYSTEM ("System configuration repository") |VirtSesRep ("Virtuoso Sesame HTTP Repository") +---------- > open VirtSesRep. Opened repository 'VirtSesRep' VirtSesRep> sparql select * from <http://localhost:8890/Northwind> where {?s ?p ?o} Limit 10. Evaluating query... +------------------------+------------------------+------------------------+ | s | p | o | +------------------------+------------------------+------------------------+ | <http://localhost:8890/Northwind/CustomerContact/ALFKI#this>| rdf:type | foaf:Person | | <http://localhost:8890/Northwind/CustomerContact/ALFKI#this>| rdf:type | northwind:CustomerContact| | <http://localhost:8890/Northwind/CustomerContact/ALFKI#this>| opl:isDescribedUsing | northwind: | | <http://localhost:8890/Northwind/CustomerContact/ANATR#this>| rdf:type | foaf:Person | | <http://localhost:8890/Northwind/CustomerContact/ANATR#this>| rdf:type | northwind:CustomerContact| | <http://localhost:8890/Northwind/CustomerContact/ANATR#this>| opl:isDescribedUsing | northwind: | | <http://localhost:8890/Northwind/CustomerContact/ANTON#this>| rdf:type | foaf:Person | | <http://localhost:8890/Northwind/CustomerContact/ANTON#this>| rdf:type | northwind:CustomerContact| | <http://localhost:8890/Northwind/CustomerContact/ANTON#this>| opl:isDescribedUsing | northwind: | | <http://localhost:8890/Northwind/CustomerContact/AROUT#this>| rdf:type | foaf:Person | +------------------------+------------------------+------------------------+ 10 result(s) (530 ms) VirtSesRep> show n. +---------- |SearchResults http://www.zillow.com/static/xsd/SearchResults.xsd |UpdatedPropertyDetails http://www.zillow.com/static/xsd/UpdatedPropertyDetails.xsd |a http://www.w3.org/2005/Atom |aapi http://rdf.alchemyapi.com/rdf/v1/s/aapi-schema# |address http://schemas.talis.com/2005/address/schema# |admin http://webns.net/mvcb/ |amz http://webservices.amazon.com/AWSECommerceService/2005-10-05 |atom http://atomowl.org/ontologies/atomrdf# |audio http://purl.org/media/audio# |awol http://bblfish.net/work/atom-owl/2006-06-06/# |aws http://soap.amazon.com/ |b3s http://b3s.openlinksw.com/

    2. Conversely the RDF4J or Sesame HTTP repository can be configured to access the repository created by the RDF4J or Sesame console. To do this the location of the data directory for both needs to be reconfigured using the Java system property info.aduna.platform.appdata.basedir (does not include RDF4J or Sesame console directory) to point to the same location. When you are using Tomcat as the servlet container then you can set this property using the JAVA_OPTS parameter. Note, if you are using Apache Tomcat as a Windows Service you should use the Windows Services configuration tool to set this property. Other users can either edit the Tomcat startup script or set the property some other way.

      * set JAVA_OPTS=-Dinfo.aduna.platform.appdata.basedir=\path\to\other\dir\ (on Windows) * export JAVA_OPTS='-Dinfo.aduna.platform.appdata.basedir=/path/to/other/dir/' (on Linux/UNIX/Mac OS X)


    Remote RDF4J or Sesame HTTP Repository Connections

    There are two methods of making a remote RDF4J or Sesame HTTP connection to a Virtuoso repository:

    • RDF4J or Sesame Remote Repository Manager class - A manager for Repositories that reside on a remote server, allowing one to access repositories over HTTP similar to how local repositories are accessed using the LocalRepositoryManager?. A connection via this method is made via the Virtuoso RDF4J or Sesame provider which will be faster and provide better support for transactions, than making a direct connection to the SPARQL endpoint using the HTTP Repository class. This is analogous to the ODBC Driver Manager in the ODBC realm for generic access to a data store via a suitable ODBC Driver.
    • RDF4J or Sesame HTTP Repository class - A repository that serves as a proxy for a remote repository on a RDF4J or Sesame server or directly to a SPARQL endpoint. This method does not make use of the Virtuoso RDF4J or Sesame Provider, using instead the HTTP protocol to make requests directly RDF4J or Sesame server or other SPARQL endpoint.

    Using the RDF4J or Sesame Remote Repository Manager class

    If a RDF4J or Sesame HTTP Repository endpoint, as detailed above already exists, the Remote Repository Manager class can be used to make a remote connection as follows by specify the URL to the remote RDF4J or Sesame HTTP Server and the RepositoryID for the repository the connection is to be made to:


    //Initialize Remote Repository Manager 
    RepositoryManager repositoryManager = new RemoteRepositoryManager( "http://hostname:portno/openrdf-sesame" );
    repositoryManager.initialize();
    
    //Set Virtuoso (or any other) repositoryID on http://hostname:portno/openrdf-sesame
    Repository repository = repositoryManager.getRepository("RepositoryID"); 
    
    // Open a connection to this repository
    con = repository.getConnection();
    
    // ... do something 
    

    Using the RDF4J or Sesame HTTP Repository class

    A direct connection to the default built-in Virtuoso SPARQL Endpoint can be made using the RDF4J or Sesame HTTP Repository class by simply specifying the URL to the Virtuoso SPARQL Endpoint i.e. http://{host}:{port}/sparql as follows:


    // Initialize Direct SPARQL Endpoint HTTP Repository connection
    String endpointURL = "http://hostname:portno/sparql";
    HTTPRepository sparqlEndpoint = new HTTPRepository(endpointURL, "");
    sparqlEndpoint.initialize();
    
    // Open a connection to this repository
    con = sparqlEndpoint.getConnection(); 
    
    // ... do something 
    

    Related