Edit
Attach
P
rintable
r9 - 2013-05-11 - 21:12:07 - Main.sbeard
You are here:
TWiki
>
Deployment Web
>
DeploymentTroubleshooting
>
PerformanceTroubleshooting
>
UnderstandingIndicesInJazz
<sticky><div id="container" > <div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/new.png" alt="new.png" width="50" height="50" align="right"/> Understanding indices in Jazz %DKGRAY% Authors: Main.GeraldMitchell <br> Build basis: Collaboration Lifecycle Management (CLM) 4.0 Jazz Team Server(JTS) 4.0 Rational Team Concert(RTC) 4.0 %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> This is guidance to understand the indices used in CLM (Jazz). ---++ Understanding Indices and Stores There are several stores and indices associated with your Jazz platform applications. ---+++ Indices and their function Indices will be a direct correlation with the performance of the application. Essentially, the index is a look-up table for the information that can be more easily queried and result in faster responses. ---+++ Query Triple store and index The query triple store index can be rebuilt using repotools command parameter -reindex scope=query. ---+++ Full Text index full text index The fulltext index can be found where ever your setting in the teamserver.properties of your application says it is located in the property __com.ibm.team.fulltext.indexLocation__ <verbatim>com.ibm.team.fulltext.indexLocation=/opt/IBM/JazzTeamServer/workitemindex</verbatim> __Note__: For high availability applications, have the Jazz Team Servers reference the same location for the full text index. To keep the index up to date and available for all servers, each server teamserver.properties should update the __com.ibm.team.fulltext.indexLocation__ in teamserver.properties to store the index for the full text on a single shared drive location. More information on the full text search can be found in [[http://www-01.ibm.com/support/docview.wss?uid=swg21586008][Technote 1586008]] ---++++ Lucene Text store and index * What is Lucene? * Lucene is an open-source full-text indexing and search engine library. * It also has other capabilities such as spellchecking and highlighting. * For more information see [[http://lucene.apache.org/][Apache Lucene]] and the [[https://jazz.net/library/article/824][Getting the most out of full text search article]] * see [[http://www-01.ibm.com/support/docview.wss?uid=swg21586008][Technote 1586008]] as well * Team Server Properties for Lucene * teamserver.properties to be aware of include __com.ibm.team.jfs.lucene.directory__ and __com.ibm.team.jfs.lucene.history.directory__. * rebuilding the Lucene index * the repotools -rebuildTextIndices commmand is used. see the [[#RepotoolsRebuildTextIndices][rebuildTextIndices]] ---++++ Performance considerations * Because the Lucene is used for a lot of lookups, to increase performance: * The Lucene Index Directory com.ibm.team.jfs.lucene.directory path should be on fast storage * The Lucene History Index Directory com.ibm.team.jfs.lucene.history.directory path should be on fast storage * The full text location should be on fast storage ---+++ Database index the database indices are .... ### fill in here ---++ repotools functions ---+++repotools reindex * Repotools-(applications) -reindex: Repository tools command to regenerate indexes. * The application must not be running before the command is run. * Use the reindex command to regenerate stores. * By default, the query triple store and the Lucene text store are regenerated * The "scope" parameter can be used to rebuild the query, the text indexes, or both. * all: to rebuild all indexes (default) - "all" in this case encompasses query triple store and the Lucene test store indexes * query: to rebuild query triple store indexes * search: to rebuild Lucene text store indexes * An example <verbatim>repotools-jts.sh -reindex scope=query</verbatim> * This parameter is useful to limit the scope of the reindex to the needed store indexes, making the reindex time shorter * The "all" parameter to reindex both live and history indices * An example <verbatim>repotools-jts.sh -reindex all</verbatim> * The "baselines" parameter is whitelist (inclusive-only) set of baselines to reindex * A comma separated list of baselines URI, without spaces. * An example <verbatim>repotools-jts.sh -reindex baseline=http://jazz.net/jts/dashboards</verbatim> * This parameter is useful to limit the reindex to the needed baselines, making the reindex time shorter #RepotoolsRebuildTextIndices ---+++ repotools rebuildIndices * Repotools-(applications) -rebuildIndices: Repository tools command to rebuild database indexes in the event of them becoming fragmented. * The application must not be running before the command is run. ( you can check using repotools command -isServerRunning) * An example <verbatim>repotools-jts.sh -rebuildindices</verbatim> ---+++ repotools compacttdb * Repotools-(applications) -compacttdb: Compact the TDB * The application must not be running before the command is run. ( you can check using repotools command -isServerRunning) * The TDB indexes can grow to be large. The compacttdb command alleviates this problem by forcing a compaction of the indexes. * srcdir The directory containing the RDF indexes to be compacted. * tempdir The temporary directory to use while compacting the RDF indexes * An example <verbatim>repotools-jts.sh -compacttdb srcdir={location of RDF indexes} tempdir={location of temporary directory}</verbatim> ---++ Possible Causes and Solutions ---+++ The queries are slow or having issues * The query triple store indexes need to be re-indexed * ---+++ The TDB needs to be compacted ---+++++!! Related topics: None ---+++++!! External links: * None ---+++++!! Additional contributors: None <sticky></div></div></sticky>
Edit
|
Attach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
:
r13
|
r11
<
r10
<
r9
<
r8
|
More topic actions...
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.