This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

FTS Configuration form in the AR System Administration Console

Note

Starting from BMC Remedy AR System 8.1 Service Pack 1, the following new terms are used for FTS plug-ins:

  • FTS Writer is called FTS Indexer
  • FTS Reader is called FTS Searcher

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 version 8.1.00
  • If you select the Upgrade option to upgrade an existing version of FTS to version 8.1.00.

    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.

If you are using FTS in a server group, the Primary and Secondary FTS plug-in processes are commented/uncommented based on your selection.

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 Port1 and Max JVM Memory1 fields for the FTS Reader and Writer instances.
    • 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 (for version 8.1 Service Pack 1 and 8.1 Service Pack 2)
    Server Group-Primary
    (for version 8.1)
    • Enter values in the FTS Port1 and Max JVM Memory1 fields for FTS Writer.
    • Enter values in the FTS Port2 and Max JVM Memory2 fields for FTS Reader.
    • If you select the Server Group-Primary option, the Primary Server Name field under Reader is unavailable because primary server name is not required for configuring FTS on the primary server.
  • Server Group-Search (for version 8.1 Service Pack 1 and 8.1 Service Pack 2)
    Server Group-Secondary
    (for version 8.1)
    • Enter values in the Primary Server Name and FTS Port 2 fields for FTS Reader. 
    • If you select the Server Group-Secondary option, the Max JVM Memory2 field under Reader and the FTS Port1 and Max JVM Memory1 fields under Writer are unavailable because from the secondary server you must connect only to the reader instance running on the primary server.

Note

A server is considered to be an indexing server if you select either the Single Server or Server Group - Primary option on the FTS Configuration form. Only the server acting as an indexing server should have the ranking in the AR System Server Group Operation Ranking form. Ranking the indexing server is essential because the other non-indexing server can determine where to failover if the configured FTS indexing server is not available.

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

FTS Port1

Enter the FTS port for primary server. The port range is 9988 - 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.

Max JVM Memory1

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

Indexer Server Name (for version 8.1 Service Pack 1 and 8.1 Service Pack 2)

Primary Server Name (for version 8.1)

Enter the name of the primary server or Indexer server.

FTS Port2

Enter the FTS port for secondary server. The port range is 9977 - 9982.

For more information about port numbers, see Understanding port numbers.

Max JVM Memory2

Enter the JVM heap size (in megabytes) for secondary 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 pluginsvr_conf.xml file.
    Applicable for Service Pack 1

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Jeffrey Mangan
    That is not what the configuration screen looks like in 8.1.01 
    Sep 18, 2014 02:39
    1. Prachi Kalyani

      Hello Jeffrey,

      Thank you for bringing this to our notice. I have updated the screen-shot.

      Thanks,

      Prachi

      Sep 19, 2014 12:29
  2. John Grunder

    The parameters here don't match the options on the FTS Configuration form in 8.1 SP2.  For Server Configuration, the options are now: Single Server, Server Group-Indexer, and Server Group Searcher.  This document does not appear to map the old settings of Server-Group-Primary and Server-Group-Secondary to these new parameters. 

    Feb 06, 2015 12:19
    1. Sujata Pawar

      Hello John,

      Thank you for pointing out this issue with the content. We have corrected the topic with your feedback.

      Regards,

      Sujata

      Feb 11, 2015 12:16
  3. Sameer Alomari

    Server-Group-Primary and Server-Group-Secondary parameter is still referenced

    please  correct it as the current parameters is Single Server, Server Group-Indexer, and Server Group Searcher

    Apr 09, 2015 05:10
    1. Prachi Kalyani

      Hello Sameer,

      The Server-Group-Primary and Server-Group-Secondary parameter are still available for BMC Remedy AR System version 8.1.

      The Single Server, Server Group-Indexer, and Server Group Searcher parameters were introduced from BMC Remedy AR System 8.1 SP1.

      So we still have the reference of these old parameters. We have updated the documentation to reflect the introduction to the new parameters.

      Thanks,

      Prachi

       

      Apr 09, 2015 05:59
  4. Carlos Aragon

    Hi 

    What processes sould be up in a "Single Server"  mode. This is because I can see 2 fts lines in armonitor.cfg.

    Thanks

    Apr 20, 2015 04:32
    1. Prachi Kalyani

      Hello Carlos,

      I will verify this with the concerned SME and will get back to you.

      Thanks,

      Prachi

      Apr 21, 2015 07:30
    1. Ash Hall

      Carlos Aragã³n, I believe that in a single server setup, only the first plugin should be enabled (named the 'Primary', the second plugin should be commented out.

      Apr 22, 2015 11:00
  5. Carlos Aragon

    Thanks Ash

    I could see an environmet that had only primary process and it works fine. I think that you are correct.

    Apr 22, 2015 06:08
  6. Viknesh Ps

    Have a doubt after reading this page.

    In our environment, the collection folder is shared and both the server pointing to the shared folder for collecting directory while configuration folder refers the local drive.

    And re indexing is running longer (more than a month) than expected (Time is derived from BMC procedure).

     

    What is recommended from BMC. The primary server should have collection directory in its local and second server should be able to access that. So colection paths will be

    Primary Server

    C:\Program Files\BMC Software\ARSystem\ftsconfiguration\collection

    Secondary

    \\Servername\C:\Program Files\BMC Software\ARSystem\ftsconfiguration\collection

     

    Similar path should be for config folder.

    Kindly clarify. And in case of collection directory not in local drive, does fts reindexing take longer time?

    Increasing heap space from 3072 to 4096 will help?

    Regards,

    Viknesh Pannirselvam

    May 01, 2017 12:52
    1. Nidhi Das

      Hello Viknesh,

      I will discuss this with the concerned SME and will write back to you.

      Regards,
      Nidhi

      May 03, 2017 04:17
      1. Anagha Deshpande

        Hello Viknesh,

        Yes, if the index collections are on a network driver, indexing is much slower than having it locally. It will be faster if the index collection is local for the primary server. Searches from secondary server should still take the same time since it refers to the index collections on a shared driver. It is indeed matter of file I/O and not much with memory. Therefore, having local indexes is faster. This is a better approach unless you are already using BMC Remedy AR System version 8.1.01.

        If you are using BMC Remedy AR System version 8.1.01, BMC recommended setup is to make use of high availability feature. For more information, see High-availability architecture for FTS. This helps secondary AR server to communicate remotely to primary plugin server and still read indexes locally. Even in this case, the index collection folder should be local on the primary server so that indexing is faster.

        Regards,

        Anagha

         

        Jun 16, 2017 12:35