System information

  • Published on Aug 8, 2025
  • 3 minute(s) read
Prev Next

Summary

System information summarizes the most important details about FactFinder integration.

  • General

  • Web components

  • Custom classes

  • Scheduled tasks

  • Paths

System information is represented as an individual page tab for System information page.

General

General section provides key operational and identification details for the FactFinder environment:

  • Essential service URLs required for system operation and monitoring are listed. This includes the primary FactFinder URL, the Analytics URL and Analytics Public URL used for accessing tracking data

  • Determining FactFinder versions. Specific version numbers are clearly displayed. This includes FactFinder version, the FactFinder UI version, Analytics version and Demoshop version. Build IDs may also be shown alongside these versions for precise identification.

  • Other important identifiers and status indicators are provided. The unique Service ID assigned to the instance is shown. The name or type of the currently Active ASO module is specified. The operational status of Multithreaded search is indicated

Reload Configuration

The application's current configuration settings can be reloaded so that to make configurations be active immediately. This action is used to apply recent modifications made to configuration files.

FactFinder automatically saves search configurations. If any changes are made directly to the configuration files instead of via the interface, these changes will only come into effect once the configuration cache refreshes.

Update logfile to disk

Log file information can be explicitly written or updated to disk storage by this button. This function might be used to ensure log data is persisted immediately or for specific diagnostic purposes.

Web components

Web components section provides status information related to integrated Web Components:

  • Security - the current state of security features applied to the web components is indicated.

  • Request Count - a metric reflecting the number of requests associated with or processed by the web components is displayed

  • Update web components Information - the information displayed in the section can be refreshed by activating this button.

Custom classes

Custom classes section details the specific classes implemented for various operations. Classes are grouped by handlers and callbacks, such as Import handler, Search callback, and System event handler.

Each category lists classes and channels where it is applied.

This information can be helpful for understanding how the application is set up and interacting with its different parts.

Scheduled tasks

Within the "Scheduled tasks" section, a comprehensive view of the automated processes running within the application instance is provided. These tasks are configured to be executed at specific intervals or times to perform essential background operations, such as data imports, system maintenance, or other recurring jobs.

Each scheduled task is listed in the grid. The following columns are included in the grid to provide detailed information about each scheduled task:

  • Type - the category or function of the scheduled task (e.g., import, maintenance).

  • Channel - the application channel to which the scheduled task applies.

  • Description - a brief explanation of the scheduled task's function.

  • Pattern - the scheduling pattern, defining when the task is set to run.

  • Next execution - the upcoming date and time when the task is scheduled to be run next.

  • Last execution start - the date and time when the task most recently began its execution.

  • Last execution finish - the date and time when the task most recently completed its execution.

  • Information - additional details or status information about the task.

Run now button allows for the specific task's execution to be manually triggered immediately, outside of its regular schedule. This capability can be useful when testing configurations or when a task needs to be initiated without waiting for its next scheduled run.

Scheduled jobs will not run for TEST and DEVELOPMENT channels.

Paths

Paths section lists important file system paths used by the application.

  • Base Resources - the directory where core application resources and configuration files are located.

  • Application logfiles - the file system location where general application log files are written.

  • SCIC tracking logfiles - the specific directory designated for storing SCIC tracking log files.

  • Search cache - the location used for storing temporary files by the search cache mechanism.

Related articles