Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

 textboxes
  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. 


    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).


  3. 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.

  4. 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,
irrespective whether they were processed earlier or not. However,
  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.
Type
  1. Enter the file name that the file event needs to verify in the File Include Criteria textbox.
Type
  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

is provided
  1. as a value

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

- Gdata
  1. – Gdata.txt and Gdata1.txt

are not required to
  1. – to be verified by the File Event

. Then
  1. , enter Gdata.txt and Gdata1.txt

file name need to be entered
  1. (separated by a comma

in
  1. ) as the value for the File Exclude

Criteria text box. To specify more than one file in
  1. Criteria field.

    Tip
    To specify multiple files in the File Include Criteria and File Exclude Criteria field, you can use regular expressions
listed in the following table
  1. .
Expression

Description

*.*

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, or but

a.txt, a.doc

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

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.

 

If more than one file is specified in the File Include Criteria text box, the process flow will trigger for each file.

 


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

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

  2. Select the Secure check box

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

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

Password text boxes respectively. This option
  1. Password field respectively. 

    This is applicable only when the

file
  1. specified

is
  1. file is located on a remote machine.

Confirm
  1. Enter the password in the Confirm Password
 text box
  1.  field.
Provide
  1. In the Event Start Date field, provide the date from which the file event will start triggering
in the Event Start Date
  1. . 
    The date must be in
MM
  1. mm/dd/yyyy format.
Click the Calendar icon and select the required date from the calendar.Provide
  1.  
  2. Select the start time from the Time drop-down list.
Provide
  1. In the Event Expiry Date field, provide the date on which file event will stop triggering
in the Event Expiry Date
  1. . 
    The date must be in
MM
  1. mm/dd/yyyy format.
Click the Calendar icon and select the required date from the calendar.Provide
  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

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

 then do
  1. , do the

following
  1. followings:

Provide

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

for
    1. at which

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

upon
    1. modification of an existing

file in the Polling Frequency field and select the
    1. file 

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

      Info
We recommended minimum
    1. Adeptia recommends that you use the Polling Frequency
to be
    1. of more than 60 seconds.


    If you select Cron

 then do
  1. , do the

following
  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:


      Days

      Description

      All Days

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

.
    1. Business Days

      The event will fire from Monday to Friday excluding holidays

.
    1. Week Days

      The event will fire from Monday to Friday

even if there are any holidays.
    1. including the holidays


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

Click Help to know more about Cron Expressions.
    1.  

  1. Provide the file stable time in

the text box and
  1. the  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
items in 
  1. the fields in the Advance Properties
 are Select the type of trigger from
  1.  section are displayed.
Image Removed
  1. Image Added
  2. In the Send Mail Notification For

box to send the mail notification.If
  1.  field, 

    • Select No Data Found On Trigger if you want to send
mail
    • email notification when
no data found on Trigger, select No Data Found On Trigger.
If
    • the file event doesn't find any data when triggered.
    • Select Error In Trigger if you want to send
mail
    • email notification
for error in Trigger, select Error In Trigger
    • if any error occurs when the file event triggers.
  1. Enter the recipient

(
  1. 's

)
  1. email address in

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

address
  1. addresses by adding comma after each email address.

  2. Select Trigger in Sequence

 check box
  1.  checkbox to trigger the

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

 check box then
  1.  checkbox, the associated

Event
  1. event will trigger concurrently.

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

then
  1. ,

select the 
  1. select Run Once

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

then
  1. ,

select the 
  1. select Ignore Misfire

 option
  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

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

.
  • Select the project in the Project field.

  • Click Save.

     

     
    1. .

    2. 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.

    Expression

    Description

    *.*

    For all the files having any extension

    *

    For all the files in a directory

    a*.txt

    For the file names that start with a and have .txt as their extension, for example, arch.txt

    a??????.txt

    For the file names that start with a and followed by six more characters and have .txt as their extension, for example, archive.txt

    a[1-9]

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

    b[aiu]t

    For bat, bit, or but

    a.txt, a.doc

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


    Info
    If more than one file is specified in the File Include Criteria field, the process flow will trigger for each file.




    Panel
    borderStylesolid
    titleYou may be interested in...
    What is new
    Application architecture
    Key terms
    Install
    Usage scenarios