IWAT for ModifyFSE

TS 5.5.2
OS WIN2K

I'm having trouble getting a iwat trigger to work consistently.

The command I'm issuing to setup the trigger is:

iwat ModifyFSE "e:\apps\interwoven\teamsite\iw-perl\bin\iwperl e:\apps\interwoven\teamsite\custom\bin\wf_checkFeeds.ipl"

I also have this one setup too:
iwat CreateFSE "e:\apps\interwoven\teamsite\iw-perl\bin\iwperl e:\apps\interwoven\teamsite\custom\bin\wf_checkFeeds.ipl"

I'm receiving a feed every night from our mainframe via FTP that successfully triggers the event. The file is processed and all is good. When I manually FTP a file into the backingstore I'm getting mixed results:

1) create is logged as CreateFSE in iwevents.log
2) renaming the file is logged as RenameFSE
3) deleting the file is logged as DestroyFSE
4) modifing (overlaying with a new version of the file) is IGNORED! No trigger no events in the log.

One more odd thing - the nightly transfer from the mainframe is never logged in the iwevents.log file. They were up until about a week ago, but I don't know what would have changed then.

- I'm really stumped about the ModifyFSE event.

So my question is:
1) what will cause a "ModifyFSE" event?
2) why would events stop being logged?

Find more posts tagged with

Comments

nipper

are you midifying a file that is checked in ? It will ONLY fire on the first modification. Due to a feature of Unix, writes happen in bunches, so large files could easily trigger multiple triggers firing. To prevent that the trigger will only fire on the modification of a file that is the same as the Staging area.

We ended up dumping the trigger for that very reason. If a file was rejected in WF and reeditied, the trigger would not fire. Caused us no end of grief.

Andy

Bowker

YIPPY ! ! !

We're in an NT world here and something in your posted made me try think....

You will only get one ModifyFSE per submit. So if you don't submit the file between modifications, you don't get another ModifiedFSE event. If you submit between changes it works like a charm!!!

As to why they are not showing up on the event log is another issue, but at least my triggers are working!

Thanks

nipper

>We're in an NT world here and something in your posted made me try think....

Here's a quarter, go buy a real OS.... :-)
Since it is the same code base for NT and Unix, the behavior will be the same.

This will likely impact the way you use the triggers. We needed something that would run whenever a file was edited (or reeditied), so this did not cut it. In a rejected WF, it would not fire.

Anyway, I think we filed an enhancement request. But it will require a timeout or some other logic to determine a true open/close rather than just the OS caching filesystem writes.

Don'e know why you do not see ModifyFSE in iwevents.log, I see plenty.

Andy