delete_jobs_on_completion=false implications

Does anyone know the implications of setting delete_jobs_on_completion=false? Are there certain files that continue to grow if this parameter is set. If so, what is the standard for clearing these files out?

I am setting this paramter to false because I want to report on workflow statistics (i.e. how long an item was in workflow for). We do not use ReportCenter.

Thanks in advance.

Find more posts tagged with

Comments

motlnt

Does anyone know the implications of setting delete_jobs_on_completion=false? Are there certain files that continue to grow if this parameter is set. If so, what is the standard for clearing these files out?

I am setting this paramter to false because I want to report on workflow statistics (i.e. how long an item was in workflow for). We do not use ReportCenter.

Thanks in advance.

I don't think so.I think the way it works is it only creates some reference files with job ids in the 'iw-store'/workflow folder.As per the manual to clear this files one can run 'iwrmjob' CLT.

Migrateduser

setting this flag to false will keep completed workflows in the system. They will not show up default in the queries unless you query by the id. In order to remove the job you'll have to run iwrmjob .

Have you tried to use report center for this purpose?

Shashi

John742

Setting this option to false does leave completed workflows in the system. It is technically not supposed to affect performance, but I am not understanding why you would want to do this anyway. What is the business need for keeping these around? Why not query the workflow info you need before you call end job? Also these jobs will not show up in active or inactive wfobj nodes when doing a iwgetwfobj. to see the jobs in a completed state use the -c param. iwgetwfobj -c.

Antharix

One reason for keeping could be for auditing purpose.