Blueprint Developer Manual / Version 2506.0
Table Of ContentsYou can migrate an existing Workflow Archive stored in MongoDB or the In-Memory store to SQL.
If enabled, the migration is performed by the Workflow Server automatically on start-up without blocking normal operation.
If data is migrated from Elastic-Core on MongoDB, the Workflow Server reads the data directly from the MongoDB. If data is migrated from Elastic-Core in Memory, the Workflow Server requests the data from the Studio Server, which holds the data in memory. The Studio Server must be running and accessible during migration.
Subject of migration are all archived processes that are stored in the completed Workflow Lists. The Workflow Server waits with the migration until these Workflow Lists have been migrated to SQL. (See Section 4.2.4.6, “Configuration for Migration of My Edited Content and Workflow Lists from Elastic Core to SQL persistence”)
To enable the migration, make sure that for the Workflow Server you
configure Elastic Core persistence as before,
configure and enable SQL persistence for Workflow Archive (see Section 4.2.4.3, “SQL Configuration for Workflow Archive”),
configure and enable Workflow Archive Migration using the following properties.
| Property | Default | Description |
|---|---|---|
|
workflow.server.archive.migration.enabled |
false |
Whether to enable migration of the workflow archive from Elastic Core to SQL persistence |
|
workflow.server.archive.migration.retry-delay |
10s |
The delay for retrying the migration of a process after an Exception |
|
workflow.server.archive.migration.skip-processes |
|
A list of numeric process ids to skip during migration (if for some reason a specific process cannot or should not be migrated) |
Table 4.7. Configuration of Workflow Archive Migration
If you migrate from Elastic-Core in Memory, you also have to set the following property on the Studio Server:
workflow.server.archive.migration.enabled=true
See also Section 3.6, “Workflow Server Properties” in Deployment Manual.
The Workflow Server stores the state of the migration and can continue after a restart if the migration has not been completed.
If migration is enabled the Workflow Server will log a message containing "Starting migration of Process archive" or "Continue migration of Process archive" when it starts with the migration. When the migration has been completed it logs a message containing "Completed Process archive migration".
