Orchestration Database Utilities

This section describes the orchestration utilities that allow you to remove orchestration workflow data from the database. There are two available utilities:

Purge utility
Renew utility

The purge utility enables you to remove completed instance data from the orchestration database. The renew utility is an alternative to the purge utility. Renew addresses situations where this is not sufficient.

Renew advantages:

Takes much less time to run.
Cleans out both definition and instance data. (Purge removes only instance data.)

Renew disadvantages:

Always removes everything from the Orchestration Engine, including active instances.
Requires more preparation to run and takes at least two steps.

Renew should be used whenever the purge utility does an inadequate job. For example, renew should be used in the following situations:

A system generates so much orchestration traffic that running purge on a regular basis is too time consuming to be practical.
A system with very frequent deployments of process apps containing orchestrations, causing the Orchestration Engine database to grow large.

If the SBM system uses orchestrations extensively or frequently, it is recommended that the Orchestration Engine database be on its own instance, separate from the Application Engine database. This allows independent database backups.