Remedy - FTS - How to FTS reindex a specific form using the Driver utility

Version 3
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    All versions of Remedy AR System Server / ITSM



    PROBLEM:

    How to FTS reindex a specific form using the Driver utility.


    CAUSE:

    N/A


    SOLUTION:

    1- In order to verify that the indexing takes place it is recommended to enable the Full Text Index Log in the Server Information > Log Files tab.

              User-added image


    2- Open the Driver tool.
          ARS 18.08.x - Using the driver program
          ARS 18.05.x - Using the driver program
          ARS 9.1.x - Using the driver program
          ARS 9.0.x - Using the driver program
          ARS 8.1.x - Using the driver program

    3- Follow these steps:

    Command: log
    Control record:
       Authentication string () :
       User name () :
     <Remedy admin user, for example Demo>
       Password () : <Remedy's user password - note, the pwd will be displayed in plain text >
       Locale[.charSet] () :
       Time zone () :
       Server () : 
    <AR Server name>

    Command: init
    INITIALIZATION

       ARInitialization  results
    ReturnCode:  OK
    Status List : 0 items


    --- The following step is only to be done if ARS is configured to use a specific AR TCP port. If the Portmapper is used then this step can be skipped --- 
    Command: ssp
    SET SERVER PORT
    The port number of server (0):
     <AR Port>
    Using private socket? (0): <RPC Socket if used, otherwise press enter>

       ARSetServerPort  results
    ReturnCode:  OK
    Status List : 0 items

    ------------------------------------------------------------------

    Command: proc
    EXECUTE PROCESS
    Command:
    Application-FTS-Reindex-Form "full_name_of_the_form" 0
    example: Application-FTS-Reindex-Form "PBM:Problem Investigation" 0
    Wait for process to complete? (F):

       ARExecuteProcess  results
    ReturnCode:  OK
    Status List : 0 items


    4- Check the FTS Index log enabled in the first step to verify the indexing is taking place for the specified form above.
    Following the example using the form PBM:Problem Investigation the FTS index log shows:
    ....................
    ....*/ Indexing request made via workflow application command [PBM:Problem Investigation, 0]
    ....*/ Sending a FT indexing message with Sequence # 139924
    ....*/ Start indexing of pending entries for indexServerName: [{AR_Indexer_server_name}]
    and greater than or equal to serverName/updateTime: [{AR_Indexer_server_name}=-300}]
    ....*/ Number of unprocessed rows in ft_pending is 1
    ....*/ Queuing indexing operation for messageData: FTSMessageData [formList=null, schemaId=2913, formName=null,
    entryId=null, seqNumber=139924, fieldIds=[0], serverName={AR_server_name}, indexServerName={AR_Indexer_server_name},
    scanArgument=0, ftsActionType=INDEX_FORM_UPDATED_SINCE, toString()=FTSMessageDataLite [seqNumber=139924,
    serverName={AR_server_name}, indexServerName={AR_Indexer_server_name}, ftsActionType=INDEX_FORM_UPDATED_SINCE,
    super.toString()=ServerGroupMessageData [messageType=null, callType=null,
    super.toString()=AbstractMessageData [serverNameOfMessageOrigin=null, delayOutsideMsgDelivery=false]]]]
    ....*/ Started processing schema re-index operation for form
    PBM:Problem Investigation initiated due to Application-FTS-Reindex-Form Sequence#:
    139924 Scan Argument 0
    ....*/ Number of unprocessed rows in ft_pending is 1
    ....*/ Scan time from user for form
    PBM:Problem Investigation is :0
    ....*/ Re-indexing started for form
    PBM:Problem Investigation
    ....*/ Total time taken to get #entries in DB for form PBM:Problem Investigation in (indexFields) is: 0:00:00.002
    ....*/ Found (25) entries to be indexed for form
    PBM:Problem Investigation using chunk approach: false
    ....*/ Indexing character field data for schema 2913, field 1000000837 with field boost 1.0, entry PBI000000000002[Frontoffice Support]
    ....*/ Indexing character field data for schema 2913, field 1000000835 with field boost 1.0, entry PBI000000000002[IT Support]
    ....*/ Indexing character field data for schema 2913, field 1000000834 with field boost 1.0, entry PBI000000000002[Calbro Services]
    ....*/ Indexing character field data for schema 2913, field 1000000232 with field boost 1.0, entry PBI000000000002[PBI_CAL_1000001]
    ....*/ Indexing data as category ArticleId for schema 2913, field 1000000232, entry PBI000000000002
    ....*/ Indexing character field data for schema 2913, field 1000000218 with field boost 1.0, entry PBI000000000002[Ian Plyment]
    ....*/ Indexing character field data for schema 2913, field 1000000217 with field boost 1.0, entry PBI000000000002[Frontoffice Support]
    ....*/ Indexing data as category OperationalCategoryTier3 for schema 2913, field 1000000065, entry PBI000000000002
    ....*/ Indexing data as category OperationalCategoryTier2 for schema 2913, field 1000000064, entry PBI000000000002
    ....*/ Indexing data as category OperationalCategoryTier1 for schema 2913, field 1000000063, entry PBI000000000002
    ....*/ Indexing character field data for schema 2913, field 1000000014 with field boost 1.0, entry PBI000000000002[IT Support]
    ....*/ Indexing data as category Company for schema 2913, field 1000000001, entry PBI000000000002
    ....*/ Indexing character field data for schema 2913, field 1000000000 with field boost 4.0, entry PBI000000000002[User needs access to specific applications.]

    --- etc----
    ....*/ Re-indexing completed for form PBM:Problem Investigation with 25 entries processed. Sequence#: 139924
    ....*/ Completed schema re-index operation for form
    PBM:Problem Investigation initiated due to Application-FTS-Reindex-Form Sequence#: 139924

    ....................
     


    Article Number:

    000100297


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles