Table of Contents

Search

  1. Preface
  2. Components
  3. Business services
  4. File listeners
  5. Fixed-width file formats
  6. Hierarchical schemas
  7. Intelligent structure models
  8. Mapplets
  9. Saved queries
  10. Shared sequences
  11. User-defined functions

Components

Components

Start and stop a file listener manually

Start and stop a file listener manually

A file listener runs at a defined frequency according to the run schedule. If you do not want to run the file listener on a pre defined schedule, you can start or stop a file listener manually.
A file listener listens to files on a defined location from the start time until the end time when you schedule a file listener run.
Consider the following file listener behavior when you start and stop a file listener manually:
  • You start a file listener before a scheduled run. The file listener that is triggered manually runs and stops at the start time of the schedule run.
  • You start a file listener after the end time of a schedule run. The file listener runs once and stops.
  • You cannot start a file listener manually when a file listener is already running according to the run schedule.
  • When the agent version is upgraded, the file listener is automatically submitted to the new agent version and the old version is stopped.
  • If the agent fails, such as a temporary network disruption, the file listener is automatically submitted to the agent when the agent restarts. Events such as
    Arrive
    ,
    Update
    , and
    Delete
    that were submitted when the agent failed are notified by the file listener when the agent restarts.
  • You stop an existing file listener run. The file listener stops listening to files for that run. A new run starts at the time of the next schedule time unless the file listener is started manually.
  • A file listener fails to start if the file listener is disabled, it is not associated to a task, or if the associated secure agent is down.
  • A file listener fails to start if the number of file events such as arrive, update, or delete, exceeds the maximum event limit.


Updated January 22, 2021