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; } } }

Too many Workflows

rwinterpacht

Does anyone have a problem with so many workflows on the TeamSite server, making the system slow to navigate? The Todo list is also very slow. By executing a iwgetwfobj, there are about 1500 workflows, of which only the most recent 200 are active.

Find more posts tagged with

Comments

Migrateduser

What version of TS are you talking about? Versions of TS prior to TS5.5.x might have problems with that many workflows. TS5.5.2+ might be able to handle that load a little better.

Migrateduser

Hi, we are on TS 5.0.1 and we also had that problem, approx 5300 jobs were floating around.... We are not using any WF's, so it was a bit of a mystery to us at first. Then we found out that our developers had forgotten to edit available_templates.cfg to exclude the new branches from the WF handling in the branch_list portion of the file.
To get rid of the massive amount of old jobs, we created a batch script where we hardcoded the highest JobID and deleted every job earlier than that ID. I've filed a feature request that lets you access the 'date-data' of the Job/Task which would make it a lot easier to delete jobs/tasks originating earlier than a certain date...
Just my 2c worth,
Hakan

Hakan

obradoa

would you mind sharing that batch script?

Migrateduser

Here is some Java that may give you ideas (maybe replace the CLT references with corresponding OpenAPI calls). Looking for my Perl version now.

package com.cmsideas.interwovenapi.utilities;

import java.io.StringReader;

import javax.xml.parsers.DocumentBuilderFactory;

import org.xml.sax.InputSource;

import org.w3c.dom.Document;
import org.w3c.dom.Node;
import org.w3c.dom.traversal.NodeIterator;

import org.apache.xpath.XPathAPI;

import com.cmsideas.CMSException;
import com.cmsideas.commandlineinvoker.CommandLineInvoker;
import com.cmsideas.commandlineinvoker.CommandLineException;

/**
* 
* Called by CommandWrapper to kill all Interwoven Workflow Jobs
* on the system by calling iwrmjob for each.
* 
*
* @author
* John West
*
* @version
* 1.0, 1/20/2003
*
* @since
* 1.0, 1/20/2003
*/

public class KillAllJobs
{

/**
* 
* Performs the processing for this utility.
* 
*
* 
* @since
* 1.0, 1/20/2003
*
* @see
* com.cmsideas.CMSException
* 
*/

public static void execute() throws CMSException
{
try
{

// Without any parameters, iwgetwfobj will return a list of all jobs in the system.

CommandLineInvoker cliCommandLineInvoker = new CommandLineInvoker( "iwgetwfobj", new Object[0] );

if ( cliCommandLineInvoker.execute() || cliCommandLineInvoker.getSTDERR().length() != 0 )
{
throw new CommandLineException( cliCommandLineInvoker.getFullErrorMessage());
}

// Loop through each job and get the Job ID.

NodeIterator objNodeIterator = XPathAPI.selectNodeIterator( DocumentBuilderFactory.newInstance().newDocumentBuilder().parse( new InputSource( new StringReader( cliCommandLineInvoker.getSTDOUT()))), "/wfregistry/workflows/id" );

Node objNode = null;
while (( objNode = objNodeIterator.nextNode()) != null )
{

// Remove the job from the system.

Integer objJobID = new Integer( objNode.getAttributes().getNamedItem( "v" ).getNodeValue());
System.err.println( "Removing " + objJobID );
cliCommandLineInvoker = new CommandLineInvoker( "iwrmjob", new Object[] { objJobID } );

if ( cliCommandLineInvoker.execute() || cliCommandLineInvoker.getSTDERR().length() != 0 )
{
throw new CommandLineException( cliCommandLineInvoker.getFullErrorMessage());
}
}
}
catch( Exception exException )
{
throw( new CMSException( exException ));
}
}
}

Edited by john on 09/16/04 11:03 AM (server time).

Migrateduser

Here's a Perl one, I didn't write this and didn't test it though.

Yikes this does exactly the opposite, removes all active jobs. Change that (commented).

use TeamSite::Config;
my $iwhome = TeamSite::Config::iwgethome();

my $xml = `$iwhome/bin/iwgetwfobj`;

my @active;

use TeamSite: Smiley Very Happy

CRnode;

my $rootnode = TeamSite: Smiley Very Happy

CRnode->new($xml);
# my @nodes = $rootnode->get_node_list('activeworkflows.id');

foreach my $node (@nodes)
{
my $id = $node->value('@v');
`$iwhome/bin/iwrmjob $id`;
print $node->value('@v') ."\n";
}

Edited by john on 09/16/04 02:20 PM (server time).

Dwayne

Or, to modify it to get rid of (or, more likely, hide) the parsing of the output of the CLT:

use TeamSite::Config;
use TeamSite::WFsystem;
use TeamSite::WFworkflow;

my $iwhome = TeamSite::Config::iwgethome();

my $wfEngine = new TeamSite::WFsystem;
my $wfRef = $wfEngine->GetWorkflows();   # or GetActiveWorkflows();

foreach my $node (@{$wfRef})
{
    my $id = $node->GetId();
    `$iwhome/bin/iwrmjob $id`;
    print $node->value('@v') ."\n";
}

Current project: TS 5.5.2/6.1 W2K

PCL5eHPGL600.txt

Adam Stoller

Here's a script I've used in the past:use strict;
use TeamSite::Config;
use TeamSite::WFsystem;

my $iwhome = TeamSite::Config::iwgethome();
my $wfs = new TeamSite::WFsystem();
my @jobids = ();
push(@jobids, $_->GetId()) foreach (@{$wfs->GetWorkflows()});
print "No Jobs to remove\n" and exit(0) if (!@jobids);
# This loop is to avoid problems where there are more jobids
# than can fit on a single command line. It slows things up
# a tiny bit, but it's better than failing outright
while(@jobids){
my $jobids = "";
while(length($jobids) < 200){
$jobids .= shift(@jobids) . " ";
}
`$iwhome/bin/iwrmjob $jobids`;
print "$jobids\n";
}
exit(0);

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Is there anyway I can remove all worklows that are 30 days older?

Thanks
Jason

shanon

well, i just modded fish's code a wee bit... thanks dude. Smiley Wink

just set NUMBER_OF_DAYS_AGO to whatever you want... i think this should work.

use strict;
use TeamSite::Config;
use TeamSite::WFsystem;

my $NUMBER_OF_DAYS_AGO = 30;

my $iwhome = TeamSite::Config::iwgethome();
my $wfs = new TeamSite::WFsystem();

my $num_days_ago = time() - ( 60 * 60 * 24 * $NUMBER_OF_DAYS_AGO );

my @tasks = map { @{ $_->GetTasks() }[0]; } @{$wfs->GetWorkflows()};
print "No Jobs to remove\n" and exit(0) if (!@tasks);

my @jobids = ( );

foreach my $task ( @tasks )
{
my $activation_time = $task->GetActivationTime();
if( ( defined $activation_time ) && ( $num_days_ago > $activation_time ) )
{
push @jobids, $task->GetWorkflowId();
}
# print "job id: " . $task->GetWorkflowId() . ", task id: " . $task->GetId() . ", activation time: " . $activation_time . "\n";
}

# This loop is to avoid problems where there are more jobids
# than can fit on a single command line. It slows things up
# a tiny bit, but it's better than failing outright
while(@jobids)
{
my $jobids = "";
while(length($jobids) < 200)
{
$jobids .= shift(@jobids) . " ";
}
`$iwhome/bin/iwrmjob $jobids`;
print "$jobids\n";
}
exit(0);

Shanon Levenherz
Mercer eBusiness Team
shanon.levenherz@mercer.com
http://www.mercerhr.com

zerovalues.pdf

Adam Stoller

Yes - write the code for accessing the information you want and determining whether it meets your criteria and plug it into the code I posted.
Read the perldoc's, Read the code, Experiment (using debugging print statements instead of actual iwrmjob execution)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

This works beatifully, thanks.
Jason