The bpm-db-cleanup Utility

The bpm-db-cleanup utility uses scripts that you can run to clean up your deployed and undeployed applications.

No installation steps are required for bpm-db-cleanup. You can run the script, using ant, from any folder that it and any related files are located in.

The utility is configured by specifying the following properties, either within the build.xml file or on the command line using the '-D' option. These properties control what deployed application is processed and what database the scripts are to be generated for. These properties are:

• tibco.config.home. The location of the config folder under the ActiveMatrix BPM installations folder.
• admin.repo. The location of the ActiveMatrix administrator folder that holds the deployed DAA information.
• template.name. The name of the application template from which the application was created.
• application.name. The name of the deployed DAA. Make sure that the application.name is correct for the deployed application as an incorrect value can leave rows in the WP tables. Check the wp_managed_archive table to verify the application name to use. The bundle name used in the wp_managed_archive table is generated using

  ${application.name}WorkPresentation${application.version}

• application.version. The fully qualified version of the deployed DAA, for example 1.0.0.201108301316.
• db.type. The type of database: mssql or oracle or db2.
• table.owner. The owner of the BPM database tables, for example amxbpm.
• batch.size. The size of a batch of rows being processed before a COMMIT is performed.