...
These are parameters that control the diagnostic tools. They may be set interactively, using the Developer Panel, or read from the developer.settingsproperties
file at startup.
The Developer Panel
...
- It enables you to change the Developer Settings without navigating away from your current page.
- It provides a visual reminder that VIVO is in Developer Mode. If a production instance were accidentally configured to run in Developer Mode, it would be easily noticed.
Entering Developer Mode
...
In the panel | Allow anonymous user to see and modify developer settings |
---|---|
In the file | developer.permitAnonymousControl |
Effect | If true , any VIVO user may change the developer settings. If false , only a system administrator (or root) may change the settings. |
The "General" tab
Freemarker settings
...
In the panel | Insert HTML comments and start and end of templates | |||||
---|---|---|---|---|---|---|
In the file | developer.insertFreemarkerDelimiters | |||||
Effect | If
|
SPARQL Query settings
Full documentation for the logging RDF Service is available here, including detailed explanation of an example log excerpt.
In the panel | LOG each query |
---|---|
In the file | developer.loggingRDFService.enable |
Effect | Write an entry to the log for each SPARQL query, assuming that
The remaining settings in this area can be used to restrict which queries are logged, or to include more information for each query. |
In the panel | Show stack trace |
---|---|
In the file | developer.loggingRDFService.stackTrace |
Effect | Each log entry will include a stack trace. The trace is abridged so it starts after the ApplicationFilterChain , omits any Jena classes, and ends at the RDFService . |
|
In the panel | Show stack trace | In the panel | Restrict by query string |
---|---|---|---|
In the file | developer.loggingRDFService.queryRestrictionstackTrace | ||
Effect | Each log entry will include a stack trace. The trace is abridged so it starts after the ApplicationFilterChain , omits any Jena classes, and ends at the RDFService . |
In the panel | Restrict by query string |
---|---|
In the file | developer.loggingRDFService.queryRestriction |
Effect | Set this to a regular expression. A query Set this to a regular expression. A query will be logged only if the text of the query matches the regular expression, in whole or in part. |
...
Link text | Show background threads |
---|---|
URL | /admin/showThreads |
The page | Displays information about the active background threads. These threads may be rebuilding the search index, re-inferencing the knowledge base, or rebuilding the Class Cache. |
Link text | Show RDF data sources |
---|---|
URL | /admin/showSources |
The page | Displays information about the triple stores, and the layers of adapters that the application wraps around them, including ModelMakers, OntModels, etc. |
The "SearchThe "Search" tab
Search query settings
...
In the panel | Restrict by URI or name |
---|---|
In the file | developer. |
Effect | Set this to a regular expression. An addition will be logged only if the list of document identifiers matches the regular expression, in whole or in part. The document identifiers are the URI and the Name fields. fields. |
In the panel | Restrict by document contents |
---|---|
In the file | developer.searchIndex.documentRestriction |
Effect | Set this to a regular expression. An addition will be logged only if the contents of the documents matches the regular expression, in whole or in part. |
In the panel | Log breakdown timings for indexing operations |
---|---|
In the file | developer.searchIndex.logIndexingBreakdownTimings |
Effect | When an indexing operation completed, write entries to the log showing how much time was taken by each indexing object: Excluders, DocumentModifiers, and UriFinders. Each entry includes
|
In the panel | Restrict by document contents Log deletions |
---|---|
In the file | developer.searchIndexsearchDeletions.documentRestrictionenable |
Effect | Write an entry to the log each time documents are deleted from the Search index, assuming that
|
In the panel | Log deletions Suppress the automatic indexing of changed triples. | |||||
---|---|---|---|---|---|---|
In the file | developer.searchDeletions.enable .searchIndex.suppressModelChangeListener | |||||
Effect | If this is selected, the search indexer will not automatically adjust to changes in the data model. This means that you can ingest data much more quickly, but you must manually request a full re-indexing when your ingests are complete.
| Effect | Write an entry to the log each time that documens are deleted from the Search index, assuming that URI s being deleted, or
|
Links
Link text | Rebuild search index |
---|---|
URL | /SearchIndex |
The page | Allows you to request a rebuild of the search index, and to monitor its progress. |
The "Authorization" tab
In the panel | Write policy decisions to the log |
---|---|
In the file | developer.authorization.logDecisions.enable |
Effect | Write an entry to the log for each policy decision that is made for any requested action, assuming that
The remaining settings in this area can be used to restrict which queries are decisions are logged, or to include more information for each decision. |
...