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 Configuration form in the AR System Administration Console

You can use the AR System Administration FTS Configuration form to configure Full Text Search (FTS). You can access this form from the BMC Remedy AR System Administration Console.

You must configure FTS manually using the AR System Administration FTS Configuration form in the following scenarios:

  • If you select the Install option to install FTS.
  • If you select the Upgrade option to upgrade an existing version of FTS.

    Note

    After completing the changes to this form, continue with the FTS configuration. See Configuring full text search.

AR System Administration FTS Configuration form

AR System Administration FTS Configuration form fields

Field name

Description

FTS Agent

Use the FTS Agent check box to enable or disable the FTS plug-in processes in the armonitor.cfg/conf file.

If you select this check box, the FTS plug-in processes are automatically uncommented in the armonitor file. If you clear this check box and save the changes, the FTS processes are automatically commented in the armonitor file.

Using the FTS Agent check box does not require manual intervention to uncomment the FTS plug-in processes in the armonitor file.

You must restart the AR System server for the changes to take effect.

Server Configuration

Select any one of the options and perform the following:

  • Single Server — (Not a server group)
    • Enter values in the FTS Port and Max JVM Memory fields.
    • If you select this option, the fields under Reader are unavailable because on a single server only one FTS instance serves as both reader and writer.
  • Server Group-Indexer
    • Enter values in the FTS Port and Max JVM Memory fields.
    • If you select the Server Group-Indexer option, the Indexer Server Name field under Reader is unavailable because indexer server name is not required for configuring FTS on the indexer server.
  • Server Group-Searcher
    • Enter values in the Indexer Server Name and FTS Port  fields.
    • If you select the Server Group-Searcher option, the Max JVM Memory field under Reader is unavailable because from the searcher server you must connect only to the reader instance running on the indexer server.

Note

Only the server acting as an indexing server should have the ranking for Full Text Operation in the AR System Server Group Operation Ranking form.

For more information, see Configuring full text search for a server group.

FTS Port

Enter the FTS port for indexer server. The recommended port range is 9977 - 9998.

During installation, the installer picks the available port from the port range starting from the lower port number. For more information about port numbers, see  Understanding port numbers  in BMC Remedy ITSM Deployment documentation.

Max JVM Memory

Enter the JVM heap size (in megabytes) for indexer server.

Indexer Server Name

Enter the name of the indexer server.

FTS Collection Directory

Enter the full path of the FTS Collection directory.

FTS Configuration Directory

Enter the full path of the FTS Configuration directory.

Notes

  • You must log on to each server and perform FTS configuration on each server using the FTS Configuration form.
  • You must restart the AR System server for the changes made to this form to take effect.
  • Ensure that the Collection and Configuration directories are available on a local drive of each indexing server. 
  • Log on to each server and ensure that the paths of the Collection and Configuration directories are identical on all the servers in the server group. For example, if the indexing servers in a server group are running on Windows and the paths of these directories are C:\data1\BMCData\BMCARSystem\FTS\Collection and C:\data1\BMCData\BMCARSystem\FTS\Configuration respectively, ensure that all reader servers have the same path set in their ar.cfg conf file with respect to the location of the Collection directory on the indexing servers. The fail-over fails if the directory paths are different. All indexing servers and reader servers in a server group refer to this path in the ar.cfg conf file. The indexing servers also refer to this path for the FTS plug-ins in the AR System Administration: Plugin Server Configuration form. 

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.

Related topic

Enabling plug-ins

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

Comments

  1. Colin Rolls

    this article should be tagged as "full text search" also as it doesn't appear when searching

    Apr 14, 2016 04:14
    1. Prachi Kalyani

      Thank you, Colin.

      I have added the relevant search terms. The topic should now be searchable.

      Thanks,

      Prachi

      Apr 14, 2016 04:52
  2. Colin Rolls

    what if i'm implementing a high availability solution with 2 separate collections, for a server group-searcher in the FTS Collection directory how can i specify both collections?  or when it fails over i need to change this to another directory?

    May 05, 2016 05:45
  3. Nerella Nerella

     HI,

    In Server Group HA when fail over happens, the searcher will automatically access the other collection directory of Indexer 2 [as per the ranking form] and will serve for the searches.

    For example :- I have 3 servers in Server Group.

    Server 1 is a indexer server with rank1 and has a collection directory on the same server.

    Server2 is a indexer server with rank2 and has a collection directory on the same server.

    Server3 is a searcher server with rank null and FTS config form will be configured with the collection directory of Server1 [Indexer Server].

     

    Initially when we do searches on Server3, Server3 will access the collection directory of Server1 and will serve the search requests.

    When server1 is down, at that time when we do searches on Server3, as server1 is down, automatically Server 3 will access the collection directory of the next indexer server [Server2] and will serve the search requests.

    May 06, 2016 03:52
  4. Colin Rolls

    OK so when you say Server 3 will be configured with the collection directory of server 1 how do you do that exactly? by specifying a shared drive such as "\\server1\full text search" folder in the config? , for example:

    Server 1 and 2 have say F:\Full Text Search  folders with replicated data in F:\Full Text Search folder , this is the index data for HA and replicated on both.

    Server 3 does not have an F:\Full Text Search folder as it's a searcher, setup would be like this below?

    Server 1 Indexer: Collection Directory in config = "F:\Full Text Search"

    Server 2 Indexer: Collection Directory in config = "F:\Full Text Search"

    Server 3 Searcher: Has no F:\  so do I put "\\Server 1\Full Text Search" in the Collection directory in the config?? but then this hard references the server 1, how will it possibly go to server 2?  I can't put "F:\Full Text Search" in the folder as i'm getting NULL pointer errors.

     

     

    May 13, 2016 04:05
  5. Colin Rolls

    I think the answer is that in Server 3 config specify the "Indexer Server Name" to be one of the Index Servers, that way the Collection directory specified will relate to that server and don't need to use a shared drive and can just type "F:\Full Text Seach" . Trying it now.

    May 13, 2016 04:46
  6. Tushar Khanwalkar

    Hi,

     We are facing a strange issue in the FTS Configuration form while enabling the Server Group Indexer i.e. by default this is set to Single server, when we select the Server Group  indexer and Save it, the setting doesn't get saved & reverts to the Single Server selection. Moreover here we even see the Searcher trim box along with Reader trim box, is this a known issue?

     

    Thanks

    Tushar Khanwalkar

    May 19, 2016 02:02
    1. Prachi Kalyani

      Hello Tushar,

      We are verifying this with our technical team. We will get back to you soon.

      Thanks,

      Prachi

      May 19, 2016 04:42
  7. Nerella Nerella

    Hi Tushar,

    This is not a known issue,

    can you please let me know, which client are you using to access the FTS Configuration form

    it is a mid tier or user tool.

    May 19, 2016 04:57
    1. Tushar Khanwalkar

      HI Prachi, it happened to be because of the faulty installation, we ran the installer again and issues got fixed. sorry for delayed response.

      Thanks

      Jun 14, 2016 04:19
  8. Matthew Savino

    On this page, the "FTS Port" Field Name Config Item has description:

    "Enter the FTS port for indexer server. The port range is 9988 - 9998."

     

    Yet, if you look at the screenshot... On this same page...

    You can see the SG-Indexer Radio Button is selected...

    Then FTS Port is defined as 9977     Which is outside of the range.

    Shouldn't the screenshot show a defined FTS Port = 9988

    On the indexing server I believe both read and write are done in the same java instance on port 9988.

     

    Jun 13, 2016 01:24
    1. Prachi Kalyani

      Hello Matthew,

      We will verify this from our technical team and get back to you soon.

      Thanks,

      Prachi

      Jun 14, 2016 03:27
    1. Prachi Kalyani

      Hello Matthew,

      Sorry for the delay in response. The recommended port range for FTS is 9977 - 9998. You can specify any port that is free from this range.

      I have updated the topic to incorporate this change.

      Thanks,

      Prachi

      Jul 20, 2016 04:15
  9. Greg Whitney

    Was there a clarification to Mathew Savino's question regarding the FTS Port? Should this be within the range mentioned for SG-Indexer or is the screenshot correct?

    Jul 18, 2016 01:29
    1. Prachi Kalyani

      Hello,

      The recommended port range for FTS is 9977 - 9998. You can specify any port that is free from this range.

      I have updated the topic to incorporate this change.

      Thanks,

      Prachi

       

      Jul 20, 2016 04:16