Tuning Workflows

You customize Identity Manager workflows to facilitate and automate complex business processes with various human and electronic touchpoints.

You can use the following methods to improve custom workflow performance:

• Simplify default workflows to improve processing time (especially for bulk processing actions such as Active Sync, bulk actions, and reconciliation) by removing the callout to the Approval subprocess.

• Ensure that no infinite loops exist in your workflows. In particular, be sure that break flags are updated and properly checked in the loops that exist in approval subprocesses.

• Put fetched objects into a variable for use later if you must contact the repository for the same object multiple times.

  Using a variable is necessary because Identity Manager does not cache all objects.

• Specify TargetResources options in WorkflowServers checkoutView to restrict the number of resources that are queried for account information.

  The following example shows how to restrict the number of resources being queried for account information.

  <Argument name=’TargetResources’> <list> <string>resource name[| #]</string> </list> </Argument>

  ---

  Note –

  In the preceding example, [| #] is an optional parameter that you can use when more than one account exists on a particular resource. In most cases, the resource name is sufficient.

  ---

• Clear unnecessary view variables left by forms, especially large maps and lists. For example:

  <setvar name=’myLargeList’></null></setvar>

  The view is copied multiple times in a TaskInstance object, so large views greatly increase the size of each TaskInstance and corresponding TaskResult.

• Use resultLimit (in seconds) in the TaskDefinition, or set this option during task execution to quickly dispose of completed tasks. Large numbers of TaskInstances impact the following:

  • How taskResults.jsp in footers and some JSP^TM tasks in the Administrator interface are displayed

  • How JSP tasks are displayed

  • Querying each TaskInstance for task renaming

  • Database size

  Set the following options as needed:

  • (Preferred selection) delete — Causes an older TaskInstance of the same name to be deleted before the new task begins execution.

  • wait — Suspends the current TaskInstance until the older TaskInstance is deleted or expired due to reaching its resultLimit.

  • rename — Inserts a time stamp into the TaskInstance name to avoid naming collisions.

  • terminate — Deletes an older TaskInstance of the same name. Each currently executing TaskInstance of the same name is terminated.