Custom Reports

I have been exploring the best method to generate extremely detailed reports about various aspects of TeamSite like Workflow usage, number of times a page was modified, etc. Each report is proposed to be accessible as a seperate menu item.

I have decided to archive each workflow job into a seperate file ( using iwgetwfobj) and I will be generating reports from these archives. Is this is the best way or is there some other simple method i am overlooking here??

Also, how do i generate a report of how many times a page was modified?? One idea that comes to mind is altering the Global Reports Center application that ships along with the product. Again, is this the most effecient method?? I am sure many of you have implemented similar solutions and was hoping for some ideas.

Find more posts tagged with

Comments

Adam Stoller

I believe there is ongoing development being performed to eventually replace the current GRC/Report mechanism (unfortunately, at this time I cannot provide much more in the way of details nor expected delivery date) - but if you can provide succint information about the *kinds* of data you are looking to report on, and perhaps even the way(s) you want to be able to present it -- to Interwoven Support, they can file that information as Feature Requests for this development effort.

That being said, using iwgetwfobj, which generates XML output is a reasonable way to quickly generate a file with all the information regarding one (or more) job(s) for later reference - though of course, this needs to be performed *prior* to the 'End' of a job, as once ended, the information is no longer [easily] retrievable. Once you have it as XML, you can either parse it, or perhaps develop an XSL style sheet to allow it to be presented directly from the data.

Catching the number of times a page was modified is probably a bit more difficult. There are 'events' that can be tracked using the 'iwat' utility - some events are logged by default, others require turning on certain features within the iw.cfg file. However, be forewarned, that there is performance overhead in both generating these additional event loggings, as well as triggering the 'iwat' program to process them.

You might start by looking at the events that are currently reported during your present 'normal' work - in the iwevents.log - and start drawing up a design for which events you want to look for and what you want to do with the information once found. After you have a 'plan', then start writing the code to perform to the plan.

I wish I could provide a quick-solution, but I don't have any to offer right now - hopefully we'll be able to do something OOTB in the not too distant future.

--fish
(Interwoven, Curriculum Development)

JackIntheBox

Thanks for your reply. Using iwat is certaianly an excellent idea!!
I was wondering if you could be specific regarding the 'events' and about the 'turning on certain features within the iw.cfg file. ' We have a website of about 400 pages so ( I am guessing) the performance hit will not be too substantial given normal usage. I am trying to log page submissions in each branch.
Also, I was also thinking about using the SQLAnywhere database installed as part of the Global reporting tool, but am unsure about if the database contains information on page submissions, etc. Can someone please elaborate??

Migrateduser

I'm not sure about the GRC database, but you can write all 'submit' and 'get latest' events to the iwevents.log.

You will need to set full_submitlog=yes and full_updatelog=yes.

Then, you can use 'iwevents' CLT to get info about such an event.

You can refer to the TeamSite CLT manual for more information about setting up triggers and iwevents.

Adam Stoller

The following information is from a while ago, but I believe still accurate. It is currently missing from the documentation (reported, to be fixed in the next significant doucmentation update)

There is a set of iw.cfg entries (they all go in the [iwserver] section):

log_createfse: Turns on logging of file or directory creates.
log_destroyfse: Turns on logging of file or directory removals.
log_renamefse: Turns on logging of file or directory renames.
log_modifyfse: Turns on logging of file modifications (copies on write).

In addition, since these tend to produce a huge number of events in the events log, you can prefilter each event type using regular expressions. Set createfse_filter, destroyfse_filter, modifyfse_filter, or renamefse_filter to a set of double quoted regular expressions. If the full event line matches any of the regular expressions the event will get logged otherwise not.

The event names are CreateFSE, ModifyFSE, DestroyFSE and RenameFSE.

--fish
(Interwoven, Curriculum Development)

JackIntheBox

Thanks a lot, all of you were really helpful. I will keep you informed on my progress.

liw5215

I have tried *FSE event trigger thing. all works except for ModifyFSE, there is no ModifyFSE logged in the iwevent.log file when an existing file is overwritten.

any ideas?

Thanks

William

Sprint

Adam Stoller

I haven't played with this stuff in a long time - not sure if/why log_modifyfse isn't working ... are you sure? I suggest you contact Interwoven Support and see if they can verify the problem with you.

--fish
(Interwoven Senior Technical Consultant)

David_Imler

I would like to see an example of the regex used in the event filter that would be located in iw.cfg. I'm trying to run a custom script from the RenameFSE event based on certain workarea and only files under templatedata. This is what I currently have in my iw.cfg and the behaviour is that all renames within the specified WORKAREA are triggering the script, regardless of whether in /templatedata or not.

log_renamefse=on
renamefse_filter="/default/main/sps/external/public_site/WORKAREA/(.*)\t(/templatedata)"