delete_jobs_on_completion - side-effects?

Adam Stoller

As of TS 6.7.0, there is an option for the iw.cfg:

[workflow] 
delete_jobs_on_completion=false

This is intended to keep workflow data around for ReportCenter.

Has anyone used this?

I'm curious about side-effects / performance / etc. with respect to this

For at least several releases in the 4.x to 5.x range it was recommended to make sure that the number of tasks kept [active] in the system be kept to something less than 2500 or 25000 (I know, there's a big difference - but that's besides the point) because the more you kept, the larger the XML storage for stuff like iwgetwfobj would get (or something like that) and it would start to hurt performance.

So I'd like to know (a) if anyone is using this feature and (b) whether or not they've encountered any problems because of it.

Bill Klish

All this option means is that workflow data remains until it is consumed by TeamSite report center. It is published through the event subsystem and once it is consumed by reporting, the data is cleared from the backing store.

We had some bad side effects using mysql as the reporting database back end because Interwoven had bugs in the connection pooling code, so the connection between the databases would go down after 8 hours, thousands of events would back up and things got ugly. In addition, the DDL they used for the tables had no secondary indexing, so when we started approaching 1,000,000 rows in the Reports database, inserts were taking 4 minutes to run. This issue has been addressed in one of the recent service packs (I think).

Hope that helps.