VIVO-1723: Externalize TPF Server

chenejac / VIVOTestMigrationJIRANotClosed

0 stars 0 forks source link

Open chenejac opened 4 years ago

chenejac commented 4 years ago

Andrew Woods (Migrated from VIVO-1723) said:

This task is to externalize the Triple Pattern Fragment server from the VIVO core code base.

Exploring whether RDFServiceBasedRequestProcessorForTPFs.java works against an external triplestore, maybe a starting point.

Success of this task will be no change to the current functionality, but the relocation of the TPF code that is currently in vivo/vitro-core.

chenejac commented 4 years ago

In exploring this issue, it appears that the source project (https://github.com/LinkedDataFragments/Server.Java) from which the VIVO TPF server was imported, supports connecting to a TDB datasource. Bringing the code base slightly more up to date, the following pull-request to the standalone Server.java application is able to serve VIVO's TDB store: https://github.com/LinkedDataFragments/Server.Java/pull/56

Two options forward include:

Further updating Server.java with a new SparqlDatasource (such as: https://github.com/LinkedDataFragments/Server.js/blob/develop/lib/datasources/SparqlDatasource.js), or
Using Server.js as the TPF, connecting to VIVO's triplestore via SPARQL (https://github.com/LinkedDataFragments/Server.js)

chenejac commented 4 years ago

chenejac commented 4 years ago

Upstream pull-request merged.

chenejac commented 4 years ago

To test:

Start VIVO
Clone and build the dependency project: https://github.com/rdfhdt/hdt-java ** Note: I am trying to help the project owner in publishing to Maven Central
Clone and build: https://github.com/LinkedDataFragments/Server.Java
Create "config.json" along the lines of the attached file of that name
Run the externalized TPF server:

$ java -jar target/ldf-server.jar config.json

$ java -jar target/ldf-server.jar config.json --port 7070