Architecture of the Workflow Recovery Manager

The following figure illustrates the architecture that Siebel CRM uses to recover a Workflow Process.

As shown in this figure, the Workflow Recovery Manager architecture includes the following components:

1. Workflow Engine. The Workflow Process Manager server component runs a long-running Workflow Process. As this Workflow Process runs, the Workflow Engine saves the execution state to the Siebel database at the appropriate time.

2. Workflow Recovery Manager. A batch server component identifies the Workflow Process instance that a server failure interrupts. If Workflow Recovery Manager detects an instance that is interrupted, then it forwards this instance to the Workflow Engine. The Workflow Recovery Manager does not rerun the Workflow Process instance.

3. Database. A database stores the run state of the Workflow Process. Siebel CRM uses the persistent record to restore the run state when the Workflow Process resumes running from a failure.

4. Server Message Queue. A queue through which the Workflow Engine and the Workflow Recovery Managers sends messages.

5. Business Process Administration View. A view that allows you to manually send a request to the Workflow Recovery Manager to recover an interrupted Workflow Process.

6. Server Administration Task Management. Allows you to define a recurrence server task for the Workflow Recovery Manager. The recurrent server task requests the Server Manager to periodically scan for interrupted Workflow Processes.