Configuration - AtomGraph/Core GitHub Wiki

AtomGraph Core is configured in web.xml (usually located at /src/main/webapp/WEB-INF) using <init-param>, for example:

    <init-param>
        <param-name>http://www.w3.org/ns/sparql-service-description#endpoint</param-name>
        <param-value>http://graphity.dydra.com/graphity/server/sparql</param-value>
    </init-param>

Currently supported parameters

http://www.w3.org/ns/sparql-service-description#endpoint
SPARQL endpoint the server is operating on. This endpoint is also accessible via local endpoint proxy, e.g. http://localhost:8080/sparql
http://atomgraph.com/ns/core#graphStore
Graph Store the server is operating on. This endpoint is also accessible via local endpoint proxy, e.g. http://localhost:8080/service
http://jena.hpl.hp.com/Service#queryAuthUser
Username for authentication against the SPARQL endpoint/graph store (so far only HTTP Basic authentication is supported)
http://jena.hpl.hp.com/Service#queryAuthPwd
Password for authentication against the SPARQL endpoint/graph store (so far only HTTP Basic authentication is supported)
http://atomgraph.com/ns/core#preemptiveAuth
If set to true, preemptive HTTP Basic authentication for SPARQL endpoint and Graph Store is enabled. In this mode, credentials are included in the request even without challenge
http://atomgraph.com/ns/core#cacheControl
Value of Cache-Control response header for all responses
http://atomgraph.com/ns/core#resultLimit
LIMIT value set on SELECT queries executed against the local SPARQL endpoint, in order to limit the number of results
http://atomgraph.com/ns/core#maxGetRequestSize
The maximum size of a SPARQL Protocol GET request (in bytes). Above this limit, the client switches to POST method during query operation.
⚠️ **GitHub.com Fallback** ⚠️