Use this procedure to remove the workflow
database and its contents, including all workflows and workflow definitions
in all isolated regions.
The Remove Workflow Database command
removes all workflow tables in the selected workflow database.
The Remove All Isolated Regions
command removes only those tables directly related to the isolated regions.
Both commands free database space on the server.
The Process Configuration Console
automatically disconnects you from all isolated regions after removing
the database. Once the action is complete, you can connect to the isolated
region(s) again.
CAUTION
Misuse of this procedure has serious ramifications. If you currently
have data in your workflow database, FileNet recommends backing up all
the servers in your VWService, in case you wish to revert the VWService
to its state before the database removal.
Since the Process Configuration Console
displays only those regions accessed by a Process Router
on your Application Engine or web server,
there may be other regions existing in the workflow database which do
not appear on the Process Configuration Console.
This procedure removes all existing isolated regions in the database.
To ensure that you do not unknowingly remove an isolated region, use
the vwtool regions command
to view all initialized isolated regions in the VWService.
Although removing the workflow database removes the workflow definitions,
it does not remove the links between the definitions and the document
class or individual document in an object store or library
Select the VWService icon,
then select Remove Workflow Database
from the Action menu.
Click Yes at the prompt if you want
to continue, or No to cancel the action.
CAUTION The
following actions do not require the Commit Changes
action. These changes take place in the database as soon as you click OK. There
is no ability to undo these changes later.
Removing the workflow database
Removing all isolated regions
Removing a single isolated region
Initializing an isolated region
NOTEWhen
you perform this action, you make changes to the workflow database structures.
If you currently have data in your workflow database, FileNet recommends backing
up all the servers in your VWService prior to completing this change.