Configuring the LQM Reporting Updater

Describes how to configure the interval and other settings of the thread that updates the LQM Reporting tables (LQM Reporting Updater). For detailed information about the LQM Reporting tables, refer to the Database Model Schema.

To configure the LQM Reporting Updater settings:

  1. On the Instance Administration page, stop the application server of the instance that you want to modify.
  2. Open the SccAppServerBootConf.xml file with a text editor.
    The default path for this file is C:\Program Files (x86)\Silk\Silk Central 20.0\instance_<instance number>_<instance name>\Conf\AppServer on the application server.
  3. Locate the LQMReporting XML tag. You can modify the following settings:
    Defines the interval in seconds when the LQM Reporting tables are updated with the most current data.
    Number of test tables processed at once. The batch size determines how much memory and processor resources are used on the application server for the update process. This setting only affects MS SQL Server databases.
    Same as MSSqlUpdateBatchSize, but for Oracle databases.
    Specifies the time-out in seconds after which queries in the LQM Reporting update process are aborted. 0 or a negative value specifies that the queries never time out.
    Determines how the update process reads from the source tables. Allowed values are NOWAIT and WAIT.
    • NOWAIT: When the update process wants to read from the source tables and another process is currently writing to these tables, the update process terminates and retries the next time it is called.
    • WAIT: The update process grabs a table lock and waits until other processes have finished accessing the tables, then reads from the source tables. The advantage is that the process always executes because it doesn't have to wait until a table is unlocked. The disadvantage is that all other processes that try to access a table after the LQM update process are blocked and have to wait until the process releases the table lock.
  4. Save and close the XML file.
  5. Restart the application server.