Configuring continuous indexing

Enable the update-mode record extractor to provide continuous ClearQuest record updates to the Lucene index.
Before you begin
The update-mode record extractor, which runs under WebSphere Application Server, provides continuous ClearQuest record updates to the Lucene index. As new ClearQuest records are added, modified, or deleted, the record extractor sends these records to Solr for Lucene to index.
The following variable is used in path names in this topic:
RATIONAL_COMMON
Directory where Rational common files are installed
About this task
By default, the update-mode record extractor is disabled when it is installed under WebSphere Application Server. To enable the update-mode record extractor, perform the following steps:
  1. Edit the file web.xml, which is located in the following directory:
    On Windows:
    %RATIONAL_COMMON%\CM\profiles\cqsearchprofile\config\cells\WebSphereAppServer-cell\applications\cqtsdbcrawler.ear\deployments\cqtsdbcrawler\cqtsdbcrawler.war\WEB-INF\
    On the UNIX system and Linux:
    $RATIONAL_COMMON/CM/profiles/cqsearchprofile/config/cells/WebSphereAppServer-cell/applications/cqtsdbcrawler.ear/deployments/cqtsdbcrawler/cqtsdbcrawler.war/WEB-INF/
  2. Locate the section <param-name>config</param-name> and modify the value of <param-value> to specify the fully qualified path and name of the ClearQuest search properties XML file in your Solr home directory. For example:
    Before:
    <init-param>
    <param-name>config</param-name>
    <param-value>CQ-SAMPL-TextSearch.xml</param-value>
    </init-param>
    After:
    <init-param>
    <param-name>config</param-name>
    <param-value>D:/CQ.Solr/MySchema/Solr/CQ-MySchema-MyDB.xml</param-value>
    </init-param>
  3. Locate the section <param-name>sitename</param-name> and modify the value of <param-value>, as needed, to reflect the current site:
    • If you are not running in a ClearQuest MultiSite environment, you can leave the value as &lt;local&gt; to indicate the local site.
    • If you are running ClearQuest MultiSite, replace &lt;local&gt; with your site location. For example:
    Before:
    <!-- change the sitename to where this application is running -->
    <init-param>
    <param-name>sitename</param-name>
    <param-value>&lt;local&gt;</param-value>
    </init-param>
    After:
    <!-- change the sitename to where this application is running -->
    <init-param>
    <param-name>sitename</param-name>
    <param-value>MyMultiSiteLocation</param-value>
    </init-param>

    If you are not running ClearQuest MultiSite, &lt;local&gt; is the encoded string value of <local>. If you are running ClearQuest MultiSite, &lt;local&gt; is the site name for which you are enabling the ClearQuest full-text search feature.

  4. Locate and uncomment the following line: <load-on-startup>1</load-on-startup>. Doing so will cause the application to start with WebSphere Application Server.
    Before:
    <!-- uncomment load-on-startup will make this application 
    start with WAS -->
    <!--
    <load-on-startup>1</load-on-startup>
    -->
    After:
    <!--UNCOMMENTED TO ACTIVATE:  load-on-startup will make 
    this application start with WAS -->
    <load-on-startup>1</load-on-startup> 
  5. Restart the WebSphere Application Server profile cqsearchprofile to effect these changes. See the WebSphere Application Server Information Center for details.

Feedback