OWLIM-SE Configuration

compared with
Current by barry.bishop
on Mar 20, 2013 11:17.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (3)

View Page History
h1. Configuration Parameters

Almost all OWLIM parameters can be set both in the TTL configuration file (that will populate the SYSTEM repository) and from the command line using the Java {{\-D<param.name>=<value>}} command line option to set system properties. When a parameter is set simultaneously using both methods, the system property overrides the value in the configuration file. Some OWLIM parameters can only be set using system properties.
These list of all OWLIM parameters is here:

Once a repository is created, it is possible to change some parameters, either by changing the SYSTEM repository or by overriding values using Java system properties - both methods require a restart of the JVM or Tomcat. Some parameters can not be changed after a repository has been created. These either have no effect (once the relevant data structures are built their structure can not be changed) or changing them will cause inconsistencies (these parameters affect the reasoner). The following table explains the variations used in the table of configuration parameters:
|| Value of 'Can be changed'\\ || Meaning\\ ||
| Yes\\ | Parameters that can be changed (effective after a restart) |
| No\\ | Parameters where a change has no effect |
| {color:#ff0000}Must NOT change{color} | Parameters that must not be changed once the repository has been created - doing so will likely lead to consistent data (unsupported inferred statements, missing inferred statements or inferred statements that can not be deleted)\\ |
The following table lists all OWLIM configuration parameters:

|| Parameter || TTL || Java \-D || Can be changed \\ || Description ||
| *base-URL* | X | X | Yes \\ | _default_ *<none>*, specifies the default namespace for the main persistence file. Non-empty namespaces are recommended, because their use guarantees the uniqueness of the anonymous nodes that may appear within the repository. |