.. include:: /includes.rst.txt .. comments - headings # with overline, for parts * with overline, for chapters = for sections - for subsections ^ for subsubsections " for paragraphs * for H5 + for H6 .. _component_monitoring: Component Monitoring -------------------- .. _concurrent_users: Concurrent Users ^^^^^^^^^^^^^^^^ The Concurrent Users page lists all the active EDG sessions (or license seats). If necessary, a user's session can be cancelled from this page, which will also configure the system to deny that user's access to EDG for 30 minutes. .. _process_management: Process Management ^^^^^^^^^^^^^^^^^^ The Process Management page displays the currently active EDG threads and allows administrators to terminate them if necessary. For each thread in the list, the following information is displayed: * Internal thread identifier * Thread details; e.g. the query text * The thread’s source; e.g. the server’s SPARQL endpoint * The thread's current duration .. seealso:: To enable management of SPARQL queries, see :ref:`advanced_parameters`. .. _auto_complete_management: Auto-Complete Management ^^^^^^^^^^^^^^^^^^^^^^^^ The Auto-Complete Management page provides a way for administrators to manually rebuild the search indices used for GUI auto-complete and quick-search fields. In rare cases, manual rebuilding of these indices may be needed if an auto-complete index becomes corrupted due to updates outside of the control of EDG or other unforeseen situations. .. _query_booster_index: Query Booster Index ^^^^^^^^^^^^^^^^^^^ EDG uses an internal index to help with query optimizations. This index knows the namespaces used in each graph, in either the subject or object position of each graph's triples. The system can use this index to skip sub-graphs that cannot contain a given namespace. The Query Booster Index page can be used to view this index and to reset it if something has gone wrong and the index has become stale or corrupt. .. _search_the_edg_index: Search the EDG Index ^^^^^^^^^^^^^^^^^^^^ The Search the EDG index supports text and facet searches across all asset collections configured to be indexed by EDG. This index is rebuilt periodically: on server start up and after changes are made to the index. This page displays a list of the currently indexed graphs and allows manual rebuilding and replacing of the index. The Search the EDG index can also be rebuilt via API: `safindexconfig:RebuildSearchTheEdgIndex`. .. _geosparql_indices: GeoSPARQL Indices ^^^^^^^^^^^^^^^^^ For use with EDG GeoSPARQL support. .. seealso:: See :ref:`edg_geo_spatial_capabilities`. .. _text_indices: Text Indices ^^^^^^^^^^^^ The EDG text index supports text search in EDG tabular editors. It updates automatically, synchronously with users’ edits. The Text Indices page offers **Rebuild** and **Delete** actions which should be used mainly for special situations, such as external uploading of `.tdb` files into the workspace with a server restart. This index is associated with the EDG UI file: `projects/server.topbraidlive.org/web/2018/textindex.ui.ttlx`. See that file’s comments for further technical details. This index is *not* rebuilt upon server restart. As a result, if a project is sent from another server or the workspace is restored from a snapshot or backup, the text index should be manually rebuilt, using this page. The Text index can also be rebuilt via API: `tbladmin:RebuildTeamworkIndex`. .. _scheduled_jobs: Scheduled Jobs ^^^^^^^^^^^^^^ The Scheduled Jobs page displays the status of any active automated EDG services. To develop customized automated services, please contact TopQuadrant Professional Services. .. _count_triples: Count Triples ^^^^^^^^^^^^^ The Count Triples page allows administrators to generate and view a report that details the amount of data present in the EDG workspace. The page displays the results of the last-generated report and provides buttons to start and/or cancel the job that generates the report. The output of this job is also used to populate the triple counts displayed in the :ref:`base_uri_management` page. .. note :: The job that produces this report should be executed in off-hours, as it requires significant system resources. .. _current_ontology_optimization_caches: Current Ontology Optimization Caches ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The Ontology Optimizations page lists the active ontology caches. .. index:: SPARQL .. _log_of_sparql_function_calls: Log of SPARQL Function Calls ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The Log of SPARQL Function Calls page allows administrators to start, stop, clear, and refresh the logging of SPARQL function calls. This log is especially useful when debugging applications under development. .. _sparql_function_registry: SPARQL Function Registry ^^^^^^^^^^^^^^^^^^^^^^^^ The SPARQL Function Registry page displays a list of the URIs and types of all the registered SPARQL functions.