This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

FTS tab configuration options

This section outlines the configuration options for FTS from the FTS tab of the AR System Administration: Server Information form.

Note

To view the FTS tab on the AR System Administration: Server Information form, you should have the BMC Remedy Full Text Search license configured.

Full Text Search configuration options
(Click the image to expand it.)

FTS tab fields

Field name

Description

Disable Full Text Searching

Controls whether the server uses the full text search engine for searching. When disabled, the server uses the search capability of the underlying database. This setting does not apply to multi-form searching. For information about ignore word list, see Configuring the Ignore Words List.

FTS Collection Directory

The location in the file system where search engine index files are stored.

Note: The server group searcher server uses the pluginsvr_config.xml file, so if you change the directory in this field, update the pluginsvr_config.xml file with the correct directory path. This file is in <ARSystemInstallDir>\pluginsvr\secondary\fts.

Best Practice:

BMC recommends not to edit the pluginsvr_config.xml file manually. Perform the following steps on the FTS Collection Directory for using the Plugin Server Configuration UI:

  1. Navigate to the Server Administration Console.
  2. Open General > Pluginserver Configuration.
  3. From plugin server instance drop-down, select the secondary plugin server.
  4. From plugin configuration tab, select the plugin ARSYS.ARF.FTS.
  5. From user defined Elements table edit the setting value for setting name ftCollectionDir.
  6. Click Modify.

FTS Configuration Directory 

The location in the file system where search engine configuration files are stored. 

Full Text Search Threshold

The maximum number of search results returned from the search engine. The default value is 10,000. To limit the number of search results (because of constraints on the computer where the search engine is running), reduce the threshold.

Indexing Failure Recovery Interval

Defines the number of minutes the server waits between periodic attempts to index entries that failed to index for an unexpected reason in a prior attempt. The default value is 60 minutes.

Temporary Table Threshold

During the processing of search results, the server creates a temporary table if the number of FTS matches reaches this value. If the number of FTS matches is less than this value, the server uses the SQL IN operator for a query on an existing table. The default value is 200.

Complex Search Threshold

During the processing of search results, the server combines results from subqueries to arrive at the final result set. If the number of rows created during processing exceeds this value, the server returns an error message indicating that the search is too complex. The default value is 1,000,000.

Indexer Server Group Signal Delay

Number of seconds before a signal is sent to the server that owns the full text indexing operation (if no signal is pending). When a server is not the owner of the full text indexing operation and generates indexing work, that server signals the server that is the owner of indexing. To reduce the frequency of signals sent, the signaling is conducted on a delayed basis. When indexing is generated, the server checks whether a signal is pending. If so, the server does not need to take any action. If a signal is not pending, the server creates a pending signal to be sent in the specified amount of time. If the full text signal delay configuration value is changed, the duration of any pending delay interval does not change. The change takes effect the next time a delay interval is started. Values are

  • Default--10 seconds
  • Minimum--1 second
  • Maximum--None

Case

Defines whether full text searching is case sensitive or insensitive. This setting affects all fields indexed for full text search and affects how the indexes are built. Therefore, changes to this setting trigger an automatic re-index. The default setting is case insensitive.

Note:

  1. Ensure that the changes in this setting is applied to all the servers in a server group environment. 
  2. On the primary server, manually change the < ftCaseSensitivity></ftCaseSensitivity> tag to true in the pluginserver_config.xml file. The location of the pluginserver_config.xml file is given below:
    (Microsoft Windows) C:\Program Files\BMC Software\ARSystem\pluginsvr\fts\secondary
    (UNIX) Location:/opt/bmc/ARSystem/pluginsvr/fts/Secondary
  3. Restart all the servers in the server group to ensure that the setting are applied on the Indexer server and on the Searcher server. The results are not consistent, unless you restart all the servers in a server group.

Search Options

Defines how the server modifies qualifications received from the client. The choices are

  • Force Leading & Trailing Wildcards
  • Ignore Leading & Force Trailing Wildcards
  • Ignore Leading Wildcards
  • Remove Leading & Trailing Wildcards
  • Query Unchanged (default)

Reindex

Initiates the re-indexing of all fields selected for full text indexing. This check box is disabled if a re-index is in progress. The dialog box must be redisplayed for the check box to become active following completion of the re-indexing.

Disable Full Text Indexer

Controls whether the server processes pending indexing tasks. When disabled, indexing tasks are still recorded for processing at a later time when indexing is enabled.

Use FTS in Workflow

Controls whether the server uses full text searches when executing queries during workflow that have full text indexed fields in the qualification. By default, this option is selected. If you clear this check box, the server uses the search capability of the database.

Ignore Words List

Defines which words are ignored during indexing.

Title Field Weight

Defines the relevancy weight for the Title field of a form in a multiple-form search. (See Configuring forms for multiple-form FTS.) A value of 1 is the baseline and provides a slight boost to the relevancy weight. If you leave the field empty, the weight is 1. To increase the weight, enter a positive number greater than 1 and less than or equal to 2000. The maximum value is 2000.To decrease the weight, enter any number from 0.9 to 0.1. To see a significant difference in the relevancy score, the weight will need to be changed by increments of 100 or more.

Environment Field Weight

Defines the relevancy weight for the Environment field of a form in a multiple-form search. (See Configuring forms for multiple-form FTS.) A value of 1 is the baseline and provides a slight boost to the relevancy weight. If you leave the field empty, the weight is 1. To increase the weight, enter a positive number greater than 1 and less than or equal to 2000. The maximum value is 2000. To decrease the weight, enter any number from 0.9 to 0.1. To see a significant difference in the relevancy score, the weight will need to be changed by increments of 100 or more.

Keywords Field Weight

Defines the relevancy weight for the Keywords field of a form in a multiple-form search. (See Configuring forms for multiple-form FTS.) A value of 1 is the baseline and provides a slight boost to the relevancy weight. If you leave the field empty, the weight is 1. To increase the weight, enter a positive number greater than 1 and less than or equal to 2000. The maximum value is 2000. To decrease the weight, enter any number from 0.9 to 0.1. To see a significant difference in the relevancy score, the weight will need to be changed by increments of 100 or more.

Note: You must re-index data so that any changes to the relevancy weights are applied to the existing data.

BMC Remedy AR System does not support Full Text Search if you have read-only database. For more information on using read-only database, see Using read-only database.

1.       The location of the pluginserver_config.xml file is given below:

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Worawut Ekarat

    Will the config form be updated so that ** is put after 'Full Text Search Threshold' to avoid confusion since changing this option requires a restart? Thanks.

    Jan 10, 2016 09:30
    1. Prachi Kalyani

      Hello,

      Changes to Full Text Search Threshold option does not require a server restart. I have updated the documentation to incorporate this change.

      Thanks,

      Prachi

      Jan 11, 2016 05:30
  2. Colin Rolls

    Under FTS collection directory it states:

    Note: If you change the directory in this field, update the pluginsvr_config.xml file with the correct directory path. This file is in <ARSystemInstallDir>\pluginsvr\fts.  - 

    I don't have this folder on my servers, i have <ARSystemInstallDir>\pluginsvr\secondary\fts where the pluginsvr_config.xml is, is that the right folder?

    some reason of why exactly I need to edit this XML file would be nice, what are implications of not setting it etc., seems ridiculous to have to edit an XML file to reflect a front end change to config.

    Also in a server group with index/searchers do I need to edit all pluginsvr_config.xml files on all servers to have the correct directory or just the indexers?

    May 27, 2016 07:37
    1. Prachi Kalyani

      Hello Colin,

      We have contact our technical team. We will get back to you soon.

      Thanks,

      Prachi

      May 30, 2016 03:30
    1. Prachi Kalyani

      Hello,

      We are sorry for the delay in response.

      Following are the answers to your questions:

      • I have updated the location to the pluginsvr_config.xml file. The correct path to the location is <ARSystemInstallDir>\pluginsvr\secondary\fts. I have updated the documentation with the correct path.
      •  Since the server group searcher server uses the pluginsvr_config.xml file, so if you change the directory in this field, update the pluginsvr_config.xml file with the correct directory path. I have updated the documentation.
      •  In a server group, you don’t need to edit the pluginsvr_config.xml file in all places, you will only need to make changes to Indexer.

      Thanks,

      Prachi

       

      Jan 02, 2017 11:54
  3. Sandeep Das

    The default weights for the fields in ITSM 9.1.02 are: Title - 4, Environment - 1 and Keywords - 2. These defaults made sense in the older versions where 4 was the maximum weight possible. If the maximum weight now is 18450000000000000000 and increments of less than 100 do not make any significant impact, are the default weights still relevant? Shouldn't the Title be 400 (or higher) and Keywords = 200 (or higher) ?

    Mar 27, 2017 05:48
    1. Anagha Deshpande

      Hello Sanddep,

      I will check with the SME and will inform you.

      Regards,

      Anagha

      Mar 27, 2017 11:28
      1. Anagha Deshpande

        Hello Sandeep,

        Apologies for delayed response.

        The weights for the fields Title - 4, Environment - 1 and Keywords - 2 were decided and changed in BMC Remedy AR System 9.1. For more information see, https://communities.bmc.com/ideas/10146

        Regards,

        Anagha 

         

        Jul 03, 2017 12:48
  4. Sandeep Das

    Hi Anagha Deshpande,

    The link you provided is not helpful. I actually voted for that idea long time ago and it is specific to older versions. The defaults of 4,1 and 2 made sense when the maximum allowed weight value was 4. In the new version, the maximum allowed value has changed to 18450000000000000000. So default values of 4,1 and 2 no longer make sense. My question is: What are the recommended values of these weight fields? And shouldn't the default values be same as the recommended values?



    Jul 03, 2017 06:36
    1. Anagha Deshpande

      Hello Sandeep,

      I will check with SME and will write back to you.

      Regards,

      Anagha 

      Jul 03, 2017 10:16
      1. Anagha Deshpande

        Hello Sandeep,

        Even though huge maximum value is allowed (virtually there is no limit), default values continue to be 4, 1 and 2. These values provide a boost, but not huge boost out of the box as expected. Huge value as you pointed out is accepted by the system, but is not used practically.

        Regards,

        Anagha

         

         

        Jul 06, 2017 12:48