│ Grooper Help - Version 25.0
25.0.0017 2,127
  • Overview
  • Help Status

Import Watcher

Service Instance Grooper.Services

Schedules and executes import jobs, which load content from external sources into Grooper.

Remarks

The Import Watcher service is a critical component for all automated and user-initiated import operations in Grooper. It is responsible for picking up and executing both scheduled and ad-hoc Import Jobs, ensuring that new content is reliably brought into the repository for processing.

Import Watcher performs two two primary roles:

  • Import Scheduling: Periodically executes one or more Import Schedules, each of which defines an Import Provider and a schedule for when and how imports should occur. This is ideal for environments where new content is regularly added to monitored locations (such as file shares, email inboxes, or content repositories) and must be brought into Grooper automatically.

  • Import Job Execution: Import Watcher is responsible for processing Import Jobs submitted automatically using Import Schedules and ad-hoc jobs submitted by users from the Imports Page. Without Import Watcher running, ad-hoc import jobs will remain unprocessed.

The service runs as a Windows service and can be configured to operate only during specific hours, to avoid interfering with business operations or to comply with maintenance windows.

How It Works

  • Each Import Schedule defines the source, criteria, and timing for an import job.
  • On each polling cycle, Import Watcher checks all enabled schedules to determine if new content is available and if the schedule should run at the current time.
  • When matching content is found, an import job is created and executed, bringing the content into Grooper as batches, folders, or documents.
  • Ad-hoc Import Jobs submitted from the Imports Page are also picked up and executed by Import Watcher, regardless of the presence of any Import Schedules.
  • After import, the source content is moved, deleted, or updated to prevent duplicate imports on subsequent cycles.

Configuration and Usage

  • Add one or more Import Schedules to define what, when, and how to import.
  • Use the 'Hours of Operation' property to restrict imports to specific time windows (e.g., after hours or overnight).
  • Ensure that each Import Provider is configured to prevent repeated import of the same content. This can be achieved by deleting, moving, or updating source items after import.
  • Monitor the service using the Grooper UI or logs to track jobs created, jobs processed, and items imported.
  • Even if you do not use scheduled imports, keep Import Watcher running to ensure ad-hoc imports are processed.

Best Practices

  • Always configure your import process so that imported items are not re-eligible for import on the next polling cycle.
  • Use descriptive names and documentation for each Import Schedule to clarify its purpose and scope.
  • Test your import configuration in a non-production environment to ensure it behaves as expected.
  • Regularly review logs and job statistics to identify and resolve any issues with missed or duplicate imports.
  • In environments that rely on ad-hoc imports, ensure Import Watcher is always running to avoid delays in processing.

Impact

  • Automates the ingestion of external content, reducing manual effort and ensuring timely processing.
  • Responsible for all import job execution, including user-initiated jobs from the Imports Page.
  • Stopping or disabling Import Watcher will halt all import operations, both scheduled and ad-hoc, until the service is restarted.
  • Misconfiguration may result in duplicate imports or missed content, so careful setup and testing are essential.

Properties

NameTypeDescription
General
Service Settings

See Also

Specific TimesPolling Loop

Notification