Configuration Tab › Mapping for Configuration Browser Tabs › Triggers › File Trigger

File Trigger

File triggers support the start of operators or processes that access highly volatile data and designed to be rerun frequently, for example, every 60 seconds. The following descriptions are for fields on the General Properties tab for File Trigger.

General Properties

File trigger properties tell the Orchestrator where and how often to look for new files with names that match the configured pattern. When found, CA Process Automation parses the content and triggers the process specified in the content.

Input directory

Specifies the target directory for files that trigger processes. This folder receives trigger files from sources with write permissions.

• Enter the full path to the target directory. For example:

  C:\Program Files\CA\PAM\R30MSSQLDomain\server\c20\triggers
  

• Enter a relative path that is relative to the <install_dir>/standalone directory.

  To specify a relative path, start with a dot (.). In the following example, triggering files are added to the install_dir/server/c2o/triggers folder.

  ./triggers
  

Processed directory

Specifies the directory into which CA Process Automation moves all files that successfully trigger processes. If a file being added has the same name as an existing file, the older file is overwritten.

• Enter the full path to the Processed directory. CA Process Automation creates this directory if not present. You can create the directory anywhere.
• Enter a relative path that is relative to the <install_dir>/standalone directory, where <install_dir> is the installation directory, $installationDir.

  To specify a relative path, start with a dot (.). In the following example, successful trigger files are added to the install_dir/server/c2o/triggeroutput/processed folder.

  ./triggeroutput/processed
  

Error directory

Specifies the directory into which CA Process Automation moves all files that fail to trigger processes.

• Enter the full path to the Error directory. CA Process Automation creates this directory if not present.
• Enter a relative path that is relative to the <install_dir>/standalone directory, where <install_dir> is the installation directory, $installationDir.

  To specify a relative path, start with a dot (.). In the following example, failed trigger files are added to the install_dir/server/c2o/triggeroutput/error folder.

  ./triggeroutput/error
  

Stability timer (seconds)

The minimum elapsed time, in seconds, from the last modification for a file to become eligible to trigger a process. Consider, for example, a trigger file with a stability timer set to 60 seconds. Such a trigger file is bypassed if the file is modified 30 seconds before searching for new files.

Default: 2

Interval (seconds)

The interval in seconds with which CA Process Automation searches the Input directory for new files.

Default: 30

Input file name pattern

Specifies the file name pattern or file extension for files in the Input directory that can trigger processes. Files that do not match this pattern are never processed. The following example pattern indicates that CA Process Automation is to process only files with an extension of ".trigger".

.*.prg