OSWorkflow delegates the responsibility of loading and storing instance data to the WorkflowStore
. Later in the section we'll see the different built-in alternatives. First, we'll take a look at exactly which data is made persistent.
The data that is made persistent in OSWorkflow when you use one of the database‑backed alternatives is as follows:
Workflow entry: The instance header data, such as process name, abstract state, etc.
Current and history steps: The steps that were travelled and the one that the workflow is in.
PropertySet: The persistent instance-specific data.
The following figure displays the relationships between them.
OSWorkflow gives several choices for storing this information. It's very important that you chose your strategy carefully for maintenance and performance reasons. You can configure the persistence strategy in the osworkflow.xml
file.