nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

TeamSite triggers - modifyFSE, createFSE

Johnny

TeamSite 6.5 (no SP)
Solaris 8

I've read a number of threads on this issue, though I'm not sure if I've seen a final answer, so here goes.

I have a need in a couple different scenarios to take action when ever a file is changed in a workarea. That is create, update, delete of a file. I was looking at TeamSite triggers as one way of handling this, though they don't seem to cover everything.

- createFSE fires when you create a new file. That's good.
- modifyFSE fires only the first time (once) for a file change. That's bad - it sounds wrong.
- deleting a file?.. not sure what this would be.

Does this sound right? Does modifyFSE really behave that way? From what I experienced and what I read on devent, it seems so. But that seems wrong.
Is there a way to watch for changes in files for create, update and delete. I can see that this may have some performance issue - though I'm not sure what the extent is.

I was thinking that I may have to look into finding/creating some sort of daemon process that watches certain directories for changes. That would be non teamsite specific.

Thoughts?... thanks for your help on this.

Find more posts tagged with

Comments

dazzlad

Sorry, I'm not really answering your question here but.....

Things to watch out for:

Importing a file via CC causes a createFSE on a temp file and then a ModifyFSE to rename it, rather than just a create.

Also createFSE can be fired before file write is completed.

To figure out the behaviour of the triggers, would just recommend that you switch them on, perform a few create, update and deletes and then search the event log for the file in question.

nipper

TeamSite 6.5 (no SP)
Does this sound right? Does modifyFSE really behave that way? From what I experienced and what I read on devent, it seems so. But that seems wrong.

Thoughts?... thanks for your help on this.

Yes that is the way it works. I looked into this in great detail. From what I have heard from the OS types. Unix streams data into the file (esp large files) so a single update could be multiple opens and closes.

I ran tests and verified that it works this way (5.5 and 6.0, never 6.5). There does not appear to be way to reset the trigger to make it run except by a submit process.

Johnny

Thanks for the feedback.

I still think these are shortcomings of teamsite. How are these triggers useful then? Especially modifyFSE if it only fires once - that's not right.

These triggers should be at the teamsite level, not at the OS level.

So I need to right (or find) some sort of directory watcher that sits on top of a workarea mount. Does that sound right? I mean how have people workaround this?

Johnny

By the way - anyone know of a directory watcher? .. haven't found a decent one yet. I might have to write one with POE if there isn't anything out there for this.

nipper

Thanks for the feedback.

These triggers should be at the teamsite level, not at the OS level.

No, they have to be at the OS level.

What if I copy a file into the filesystem ? The only way it will be caught is at the OS level. After I looked at this I thought about it and decided that I only care when the FSE changes from the Staging, not each time it changes.

BTW, do you know how DAS works ? if you edit a DCR multiple times without submitting it, will it update the DB ? IIRC, it uses triggers.

Andy

Johnny

But isn't the filesystem just a virtual view of the teamsite repository? Meaning that if I copy a file into TeamSite via iwmount then it does eventually hit teamsite right?? TeamSite files are abstracted from OS files. At least that's my understanding.

I know nothing about DAS - the less the better. (can you tell I'm getting quite bitter!)

nipper

But isn't the filesystem just a virtual view of the teamsite repository? Meaning that if I copy a file into TeamSite via iwmount then it does eventually hit teamsite right?? TeamSite files are abstracted from OS files. At least that's my understanding.

Yes but.

Unix is doing a filesystem open and close. It goes through the IFS. There is no way for TS to recognize a bunch of opens and writes (which is one atomic operation to the user) from multiple opens and closes. You could do it through some TeamSite GUI operation (which was what I thought you meant) but that would miss strict filesystem access.

Johnny

ahhh this is going nowhere in my favor! Smiley Happy

Thanks for the explaination - but it still sucks! When are they ever useful?

By the way - anyone know of a directory watcher? .. haven't found a decent one yet. I might have to write one with POE if there isn't anything out there for this.