The properties in this section are used to configure the migration of CapList data from
Elastic Core (MongoDB or In-Memory replacement) to SQL persistence. As prerequisite,
SQL persistence needs to be configured with caplist.persistence=true
and Section 3.8.2, “Data Source Properties”.
The most important property is caplist.migration.enabled which has
to be set to true for the Workflow Server, User Changes Application, and
Studio Server to enable migration.
Data migration is performed by the Studio Server. If present, additional
Studio Server instances must be configured to not also start the migration
by setting their property caplist.migration.on-startup=false.
caplist.migration.enabled
Type
Boolean
Default
false
Description
Set to true to enable migration of CapList data from Elastic Core
(MongoDB or In-Memory replacement) to SQL persistence. This property
needs to be set to the same value for Workflow Server, User Changes
App, and Studio Servers. This property is only used if
caplist.persistence=sql.
caplist.migration.force
Type
Boolean
Default
false
Description
Set to true to force a restart of CapList data migration from Elastic
Core (MongoDB or In-Memory replacement) to SQL persistence, after it
has already completed. Note, that this will not remove already
migrated data from SQL persistence. This property is only used if
caplist.persistence=sql, caplist.migration.enabled=true, and
caplist.migration.on-startup=true.
caplist.migration.on-startup
Type
Boolean
Description
Whether this application performs the migration of CapList data from
Elastic Core (MongoDB or In-Memory replacement) to SQL persistence.
This property defaults to true for the Studio Server and to false for
all other applications. You only have to change this, if you start
multiple Studio Servers. In that case, all but one Studio Server must
be explicitly configured with value false. This property is only used
if caplist.persistence=sql and caplist.migration.enabled=true.
caplist.migration.skip
Type
Boolean
Default
false
Description
Set to true to skip CapList data migration from Elastic Core (MongoDB
or In-Memory replacement) to SQL persistence, as if it had completed.
This property is only used if caplist.persistence=sql,
caplist.migration.enabled=true, and caplist.migration.on-startup=true.
Table 3.40. Configuration Properties for Migration of CapLists from Elastic Core to SQL Persistence
