Resolution:
Description:
============
Is it possible to improve performance of case migration when releasing TIBCO iProcess Procedure(s) that have a high volumes of cases?

Environment:
==========
All supported TIBCO iProcess Engines.
All supporting operating systems and databases.

Resolution:
=========
It is not possible to control the case migration process, for example, by only migrating active cases and not migrating closed cases. Perform the following to reduce the time taken to migrate cases.

1). Deleted unused procedure versions before the migration. Having a large number of unused procedures can cause a significant difference in performance. This could be old procedure versions that no longer have cases associated with them.

2). Purge unwanted cases before performing the procedure release and case migration.

3). Rebuild database indexes to ensure they are operating at their optimum.

4). Use the “-M” option with the “swutil PROC RELEASE” command. To use this option the TIBCO iProcess Engine must be stopped. This will reduce the activity on the database.

Using the information from the two commands below, it should be possible to identify which procedure's versions are not being used.

To identify which procedures and versions are on the system use the following command:

%SWDIR%\util\plist –P &ltprocedure_name>

Note the upper case "P". Without the &ltprocedure_name> specified all procedures and their versions will be listed.

To identify which procedures and versions have cases associated with them use the following command:

%SWDIR%\util\plist –cvv &ltprocedure_name>

Note the “c” and double “v”. The &ltprocedure_name> must be specified. Example output is as follows:

C:\swserver\ipe11114&gtutil\plist -cvv CARPOOL
CNum  CID   Sts  Case Description         Starter           yyyy/ddd hh:mm     PVer PPrc
------------------------------------------------------------------------------------
1         1     LIVE case 01 ver 1.0          administrator@staffw_nod2       1.0  umr
51        51   LIVE case 02 ver 1.0          administrator@staffw_nod2       1.0  umr
101       101 LIVE case 01 of ver 1.1       administrator@staffw_nod2       1.1  umr
151       151 LIVE case 02 of ver 1.1       administrator@staffw_nod2       1.1  umr

In this example the procedure CARPOOL has four cases with two cases using version 1.0 and two cases using version 1.1. The procedure version number is the second from the last column.

References:
==========
TIBCO iProcess™ swutil and swbatch Reference Guide.

Is it possible to improve performance of case migration when releasing TIBCO iProcess Procedure(s) that have a high volumes of cases?