EVENT File watchers?

[Kenneth Chrapczynski]

CA/WA DE - I have an application that has six file watcher events that can trigger a series of jobs. A couple times a year the vendor sending the files to us has an issue where the volume is greater than their process can handle and it breaks. By the time they fix their process over 3,000 files have queued up. When they send these files over 3,000 applications are triggered into the queue and cause heap issues and freeze up espresso.

 

Does anyone know of a better way to design an application that won't trigger in multiple generations of the same application into the active queue?

 

I was thinking of breaking this application into six applications (the files are landing in six different folders). Change the event to a scheduled daily event, having the file watcher be the first process in the flow, once a file is detected run the job flow and re-trigger itself until all files are consumed.

[SHARON SHIMANEK]

Hi,

We have many file triggers that watch for multiple files at the event level.  On the application properties we check

DO NOT TRIGGER IF ACTIVE.  On the event, file trigger tab we put NO Changes for X min (ususally 5 or 10).  We choose time based on how long it usually takes to get all files.  then the event triggers the application and the job processes all files at once.

 

Sharon

[Kenneth Chrapczynski]

Hi Sharon, Thanks for the reply. I saw the option on Application/Properties in the manual, but as noted below #3 it only talks about skipping the next scheduled execution so I didn't think it applied to an Event File Trigger. We do have the "Wait for previous generation" selected, but that doesn't prevent all generations from scanning into the active queue. We do have the time values set in the event file trigger for size and no changes.

 

Our Application has 14 jobs in it and needs to process each file received independently, it can't process all the files in a single applications execution. 

 

Prevent Events from Triggering While the Current Generation is Running

You can prevent Application generations from running concurrently by preventing Events associated with the Application from triggering while the current generation is running.

Note: An Application can be triggered by multiple Events, each with its own scheduling criteria. If you want to prevent a specific Event associated with the Application from triggering while the current generation (triggered by the same Event) is running, you can use a similar option at the Event-level.

Follow these steps:

1. Open the Application in the Define perspective.

The Application appears in the workspace.

2. Right-click the Application in the Application Workspace view, and select Properties from the pop-up menu.

The Basic page of the Application properties dialog opens.

3. Select the Do not trigger if active check box and click OK.

If a generation of the Application is running and the next scheduled execution of its associated Event occurs, the server does not trigger the Event, causing the Event to miss its scheduled execution time. The Event triggers at its next scheduled time when the current generation completes.

[SHARON SHIMANEK]

yes that is all true.  That is why we put X min on the file monitor to no trigger until there was no activity for several minutes.  Most of our jobs that are in the application triggered by the file trigger run really quick so it has not been an issue for us.