litvinovg/vivo
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

VIVO-978 clarify the instructions for alternative triple stores

Browse source
This commit is contained in:
j2blake 2015-02-23 13:34:19 -05:00
parent ed239f64a7
commit ac7ef7209f
2 changed files with 16 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

20
config/example.runtime.properties
View file

@ -107,7 +107,7 @@ VitroConnection.DataSource.pool.maxIdle = 10
# -----------------------------------------------------------------------------
# USING A DIFFERENT DATA STORE
# USING A DIFFERENT DATABASE
# -----------------------------------------------------------------------------
#
@ -118,20 +118,10 @@ VitroConnection.DataSource.dbtype = MySQL
VitroConnection.DataSource.driver = com.mysql.jdbc.Driver
VitroConnection.DataSource.validationQuery = SELECT 1
#
# Optional URI of a SPARQL endpoint from which VIVO should display data.
# If set, VIVO will use this endpoint as its triple store instead of the
# SDB database.
#
#VitroConnection.DataSource.endpointURI =
#
# Optional URI to use for modifying the above endpoint via SPARQL UPDATE.
# This setting is only necessary if the endpoint does not support updates via
# its main URI. (This may be done for access control purposes.)
# If the endpointURI above is not set, this setting has no effect.
#
#VitroConnection.DataSource.updateEndpointURI =
# Note: the above parameters allow you to change the relational database that
# is used as the back end for Jena SDB. If you want to use a triple store
# other than SDB, you will need to edit applicationSetup.n3. See the
# installation instructions for more details.
# -----------------------------------------------------------------------------