Versions Compared

Old Version 7

changes.mady.by.user Jim Blake

Saved on

compared with

New Version Current

changes.mady.by.user Benjamin Gross

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

...

  1. It enables you to change the Developer Settings without navigating away from your current page.
  2. 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.

No Developer PanelDeveloper Panel (closed)

Image Removed

 Image Added

Entering Developer Mode

...

In the panelAllow anonymous user to see and modify developer settings
In the filedeveloper.permitAnonymousControl
EffectIf true, any VIVO user may change the developer settings. If false, only a system administrator (or root) may change the settings.

The "General" tab

Image RemovedImage Added

Freemarker settings

...

In the panelInsert HTML comments and start and end of templates
In the filedeveloper.insertFreemarkerDelimiters
Effect

If true, you may view the HTML source for a VIVO page to see which Freemarker templates were used to create each portion of the page. For example:

Code Block
languagexml
...
<!-- FM_BEGIN view-search-default.ftl -->
<a href="/vivo/display/n2252" title="individual name">Oswald, Jeremiah</a>
        <span class="display-title">Faculty Member</span>
<p class="snippet"></p><!-- FM_END view-search-default.ftl -->
...

SPARQL Query settings

Full documentation for the logging RDF Service is available here, including detailed explanation of an example log excerpt.

In the panelLOG each query
In the filedeveloper.loggingRDFService.enable
Effect

Write an entry to the log for each SPARQL query, assuming that INFO-level logging is enabled for the RDFServiceLogger. Each entry includes

  • The time spent executing the query
  • The name of the method on RDFService that received the query
  • The format of the result stream from RDFService
  • The text of the query.

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 panelShow stack trace
In the filedeveloper.loggingRDFService.stackTrace
EffectEach 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.
Note

The configuration models (display, user accounts) and the TBox models are memory-mapped. This means that any "read" operations are run against a cached copy of the model, and are not logged. For these models, only "write" operations are logged.

The ABox models are not memory-mapped; both "read" and "write" operations will be logged.

In the panelShow stack traceIn the panelRestrict by query string
In the filedeveloper.loggingRDFService.queryRestrictionstackTrace
EffectEach 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 panelRestrict by query string
In the filedeveloper.loggingRDFService.queryRestriction
EffectSet 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 textShow background threads
URL/admin/showThreads
The pageDisplays 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 textShow RDF data sources
URL/admin/showSources
The pageDisplays information about the triple stores, and the layers of adapters that the application wraps around them, including ModelMakers, OntModels, etc.

The "SearchThe "Search" tab

Image RemovedImage Added

Search query settings

...

In the panel Restrict by URI or name
In the filedeveloper.searchIndex.uriOrNameRestriction
EffectSet 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 filedeveloper.searchIndex.documentRestriction
EffectSet 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 filedeveloper.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

  • The display label of the indexing object
  • The number of times that the indexing object was invoked
  • The total time required for the indexing object
  • The average time for each invocation of the indexing object

In the panel Restrict by document contents Log deletions
In the filedeveloper.searchIndexsearchDeletions.documentRestrictionenable
Effect

Write an entry to the log each time documents are deleted from the Search index, assuming that INFO-level logging is enabled for the SearchEngineLogger. Each entry includes

  • The time spent deleting the documents
  • Either
    • the list of URIs being deleted, or
    • the search query that was used to find documents for deletion
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 deletions Suppress the automatic indexing of changed triples.
In the filedeveloper.searchDeletionssearchIndex.enablesuppressModelChangeListener
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.

Note

This doesn't really belong in the developer panel, since it changes the way VIVO operates. It was put here to answer an urgent requirement

Effect

Write an entry to the log each time that documens are deleted from the Search index, assuming that INFO-level logging is enabled for the SearchEngineLogger. Each entry includes

  • The time spent deleting the documents
    • Either
  • the list of URIs being deleted, or
    • the search query that was used to find documents for deletion

    .

    Links

    Link textRebuild search index
    URL/SearchIndex
    The pageAllows you to request a rebuild of the search index, and to monitor its progress.

    The "Authorization" tab

    Image RemovedImage Added

     

    In the panelWrite policy decisions to the log
    In the filedeveloper.authorization.logDecisions.enable
    Effect

    Write an entry to the log for each policy decision that is made for any requested action, assuming that INFO-level logging is enabled for the PolicyDecisionLogger. Each entry includes

    • The requested action
    • The name of the policy
    • The decision and message.

    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.

    ...

    In the panel Restrict by policy name
    In the filedeveloper.authorization.logDecisions.userRestrictionpolicyRestriction
    EffectSet this to a regular expression. A decision will be logged only if the string value of the policy matches the regular expression, in whole or in part.
    In the panel Restrict by user identifiers
    In the filedeveloper.authorization.logDecisions.policyRestrictionuserRestriction
    EffectSet this to a regular expression. A decision will be logged only if the list of user identifiers matches the regular expression, in whole or in part.

    ...