Originally posted by: johnxp

Hi anyone can help on this?

We set the MapDelay to 2 seconds and place 1 thousand files in folder at one shot. WTX waited 2 seconds before processing each file.

I thought WTX would check every file, and if the file already exists in the folder for more than 2 seconds, it will be processed.

That means WTX would wait for 2 seconds for the first file only, the rest should be processed immediately. Looks like MapDelay is not right for this purpose.

Our intention is to have WTX wait for 2 seconds after the file being created/copied in the folder to prevent file contention issues.

Any other settings can do this without performance impact?

Originally posted by: GertieKearney

Hi,

Have you tried to set TriggerTime in the Dtx.ini file. The following link is documentation link.

https://www.ibm.com/support/knowledgecenter/en/SSVSD8_9.0.0/com.ibm.websphere.dtx.es.doc/references/r_event_server_TriggerTime.htm

If the TriggerTime is set to 2, and a non-uniquely named file was being written to a directory as a trigger, the timestamp would have to have a minimum of a 2 second difference or it wouldn't trigger.

Gertie.

Originally posted by: johnxp

Hi Gertie,

I changed MapDelay to 0 and set TriggerTime to 15 (for testing purpose), but when I copied 10 files to the folder, all files got processed almost immediately, there was no waiting time for 15 secs as I expected. What file time was WTX checking (Created/Modified/Accessed)? When I copy/move a file, the Created time will be changed.

Originally posted by: GertieKearney

Hi,

The following Technote 'How to prevent Launcher from triggering multiple times on same input file' might be useful.

http://www-01.ibm.com/support/docview.wss?uid=swg21247970

Gertie.

Originally posted by: johnxp

That Technote is not very helpful to me.

I want to use some settings like, for example, set trigger time = 10 secs, if a file is placed now, WTX will not be triggered until 10 seconds later. WTX should measure the difference between the creation time and current time. 

Originally posted by: PaulBrett

With MapDelay, the trigger occurs instantly, but the map does not run until the specified MapDelay time has passed.  A MapDelay of 15 seconds would mean that after dropping 1000 files in, after a 15 second delay the maps should start to process all those files (concurrently up to the maximum allowed, should multi-threading be enabled).

My guess is that you did not have multi-threading enabled (maybe you had one of the trace files set to a fixed file name, or were using workspace=files instead of workspace=memory).

Thank you

Paul

Follow me on Twitter