Page Comparison

The File Event enables you to specify when and how frequently a process flow should be executed based on either the creation of a new file, or existence of a file(s) in a pre-defined location, or upon its modification.

Steps to create a File Event Activityactivity

1. Click Configure > EVENTS > File Event.
   

2. Click CREATE File Event.
   

3. On Create File Event screen, enter the name and description of the new JMS Event in the Name and Description

1.  fields respectively.
   

Image Removed

1. Image Added

2. Select the trigger type from the Trigger Type drop-down list. The available options are On FileCreated, On FileExists, and On FileModified.

1.  

   
   

   Trigger Type Selection	Description
   On FileCreated	To configure the file event to check for the creation of a new file(s).
   On FileExists	To configure the file event to check for the existence of the file(s).
   On FileModified	To configure the file event to check for any modification in the file(s).

   
   

2. Select Check for File Modification check box if you want to process the files that are modified after creation. This option is enabled only if On FileCreated option is selected in the Trigger Type drop-down list box.
   
   

3. Select Run Initial Load check box if you want to process the files that are created when the event is not active. This option is enabled only if On FileCreated option is selected in the Trigger Type drop-down list box.

    
   After the activation of the event, for the first time, the system processes all the files that exist in the base folder location,

1. and for subsequent activations, only the unprocessed files are processed each time.

2. Select Don't Process Duplicate Files check box if you don't want to process the same file again.

3. Select Process Empty Files check box if you want to run the event even when the input file is empty.

1. Enter the file name that the file event needs to verify in the File Include Criteria textbox.

1. Enter the name of file that the file event does not need to verify in the File Exclude Criteria textbox. For example, if you enter *.txt

1. as a value

1. for the File Include Criteria field, but don't want the two files

1. – Gdata.txt and Gdata1.txt

1. – to be verified by the File Event

1. , enter Gdata.txt and Gdata1.txt

1. (separated by a comma

1. ) as the value for the File Exclude

1. Criteria field.

   Tip
   To specify multiple files in the File Include Criteria and File Exclude Criteria field, you can use regular expressions

1. .

For all files with some extension

*

For all files in a directory

a*.txt

For files starting with a and having extensiontxt(e.g. arch.txt)

a??????.txt

For files starting with a and have 6 more characters followed by txt extension (e.g. archive.txt)

a[1-9]

For a1, a2 ,a3 …………..a9

b[aiu]t

For bat, bit orbut

a.txt, a.doc

For two files named as a.txt and a.doc

For example, if you enter h*/*.txt in File Include Criteria field and C:/Gmdata inFileBase Location field, it will search for all .txt file inside all directories which starts from h under C:\Gmdata.

1. 
   

2. Provide the path of the file in the File Base Location 

1. field, for example, C:/Gmdata.

1. Select the Secure check box

1. if the File Event is secured, that is, username and password are required to access it.

1. Enter the username and password required to access the file in the User ID and 

1. Password field respectively. 

   This is applicable only when the

1. specified

1. file is located on a remote machine.

1. Enter the password in the Confirm Password

1.  field.

1. In the Event Start Date field, provide the date from which the file event will start triggering

1. . 
   The date must be in

1. mm/dd/yyyy format.

1.  
2. Select the start time from the Time drop-down list.

1. In the Event Expiry Date field, provide the date on which file event will stop triggering

1. . 
   The date must be in

1. mm/dd/yyyy format.

1.  
2. Select the expiry time from the Time drop-down list.
3. Select the type of trigger from the Trigger drop-down list. Following are the options:
   
   • Simple
   • Cron 

   By default, Simple is selected. This

1. triggers the File event as per the defined polling frequency.
   If you select Simple

1. , do the

1. followings:
   

1. 
   

   1. In the Polling Frequency field, provide the time interval

1. 1. at which

1. 1. the file event will check for the arrival of any file or

1. 1. modification of an existing

1. 1. file . 

1. 1. Select the unit of time (seconds, minutes or hours) from the Duration drop-down list.
      
      

      Info

1. 1. Adeptia recommends that you use the Polling Frequency

1. 1. of more than 60 seconds.

      
      

   If you select Cron

1. , do the

1. followings:

   1. Select the days of the week on which the event should fire from the Firing Days drop-down list.  Following are the available options:

1. 1. 
      

      Days	Description
      All Days	The event will fire on all days (Mon to Sun) of the week

1. 1. Business Days	The event will fire from Monday to Friday excluding holidays

1. 1. Week Days	The event will fire from Monday to Friday

1. 1. including the holidays

      
      

   2. Define the frequency of execution (in Cron Expression) in the Firing Schedule.

1. 1.  
      
      

2. Provide the file stable time in

1. the File Stable Time field, and select the duration from the drop-down list. 

   Info
   This is the wait time given for the file to get stable. Event waits for the given time before getting fired. This option is applicable for On FileCreated and On FileModified Trigger Type. The trigger will wait for the specified time for the file to become stable.

   
   

2. Click Advanced Properties to expand the hierarchy. All

1. the fields in the Advance Properties

1.  section are displayed.
   

Image Removed

1. Image Added

2. In the Send Mail Notification For

1.  field, 

   • Select No Data Found On Trigger if you want to send

1. • email notification when

1. • the file event doesn't find any data when triggered.
   • Select Error In Trigger if you want to send

1. • email notification

1. • if any error occurs when the file event triggers.

2. Enter the recipient

1. 's

1. email address in

1. the Notification Receiver Email-ID(s) field. You can add multiple email

1. addresses by adding comma after each email address.
   

2. Select Trigger in Sequence

1.  checkbox to trigger the

1. event in sequential manner. If you do not select the Trigger in Sequence

1.  checkbox, the associated

1. event will trigger concurrently.

2. If you want to enable misfire handling for your JMS event

1. ,

1. select Run Once

1.  from the Action on Misfire Event drop-down list. If you do not wish to enable misfire handling for your file event

1. ,

1. select Ignore Misfire

1. .

    

   
   

   Info
   The Run Once option will run only one collective instance of all the misfires for a particular event. Whereas, the Ignore Misfire option will not run a misfired event.

   
   The default value

1. for Action on Misfire Event field is set to Run Once for all of the earlier events.

2. Click Save.

Click Save.

Anchor
regex regex

Using regular expressions

You can use regular expressions described in the following table when you want to specify more than one file in the File Include Criteria and File Exclude Criteria field. For example, if you enter h*/*.txt in the File Include Criteria field and C:/Gmdata in the File Base Location field, it will search for all .txt files that start with h inside all the directories under C:\Gmdata.