File Integration Process (IP) run when a specified file is transferred
to, created in, or modified in a specified directory. The file may
or may not be the data source for the data translation specification (DTS) files (*.dts),
so the available options vary accordingly. Use File IP settings with
File-based IPs.
To display the Event Settings tab for a File IP, in the Console, expand the console node, expand the Integration Server node, and select Integration Processes.
Specify file IP settings
In Event File, enter or browse to the file(s) that the IP is to poll for. You can include:
One or more wildcard
(*) characters to allow a range of files in a specified directory.
The variable <ANDNOT> to monitor two
different files. For example, file1.txt
<ANDNOT> file2.txt instructs the IP to wait until file1.txt
either appears or is modified, then triggers the job to run only when
another specified file file2.txt
is either not present or deleted.
Specify, in seconds, in Poll for event file every how frequently the IP should poll the event file while the IP is active. Polling can be set to be performed from between 1 to 9999 seconds. The default polling frequency is 60 seconds.
Note: When you are
configuring File Management security, always select UNC if both a UNC
and physical path appears in the dialog box. For example, if the dialog
box displays C:\Temp and \\[machine name]\Temp,
select \\[machine name]\Temp as the folder
path.
In Event File Handling, select the action to take on the event file. Specify one of:
Obtain
a lock on event file before processing — Lock the event file after
the corresponding job is queued. This prevents the file from being overwritten
while it is in the queue. The file automatically unlocks after the job
completes. The Console does not look for the file while the job is in
the queue, and begins polling again when the job completes.
Note: For a File IP, you must clear this option before you can modify the Processor Group on Step 1 — Process Type.
Rename
event file to a unique name — Rename the event file to a temporary
name after the corresponding job queues. Therefore, you can replace the
original event file while the job is queued because the Console uses an
alias for the trigger file name. The renamed file includes the event ID
appended to it. For example, ABC.txt becomes ABC.txt.L001.
Note: Do not
use this option if the event file is also the source for the job. The
DTS
stores the name of the source and cannot open the source if it is renamed
by this process.
Auto
recovery of renamed files — Queue the renamed event files
when system startup occurs. This is similar to the Run If Past Due option for Time IPs.
Delete
event file after execution — Delete the event file after the job
is run. If the file served only as a flag to start the job execution,
you may want it deleted to prevent hard disk clutter. You may also need
to select this option if the event file uses wildcards.
You can create a batch file, a Visual Basic or other program,
or VBScript to control what happens to the event or source files. Then,
use pre and post processing commands
to execute.
An example VBScript for file handling is included in the
Sample files installed with the product. Use the Windows Script Host (wscript.exe)
or Command Script Host (cscript.exe) to execute VBScript. Refer to the
corresponding Windows or script host engine documentation for more information.
In DTS Execution, specify whether the IP
should continue to poll after the job is run (recurring), or if the job
executes only once.