Blueprint Developer Manual / Version 2506.0
Table Of ContentsFollow this section to use SQL persistence for all editorial features that support it and previously used Elastic Core persistence. For details, please refer to the sections below describing configuration of SQL persistence for the separate features.
The features that support SQL persistence are:
notification: Notificationsproject: Projectscaplist: Workflow Lists, My Edited Contentworkflow.server.archive: Archived Workflows
The persistence for each of these features can be configured separately by switching the respective
<feature>.persistence property to sql.
Additionally each feature has its own datasource that can be configured with the <feature>.datasource properties,
except for workflow.server.archive where the existing Workflow-Server SQL connections are used.
notification.persistence=sql notification.datasource.url=jdbc:mysql://mysql:3306/cm_notifications notification.datasource.username=cm_notifications notification.datasource.password=cm_notifications
Example 4.29. SQL Persistence Configuration for notifications
The datasources are configured by default in the application properties of the respective applications.
But, the persistence properties are currently set to elastic-core by default, which means
by default MongoDB or In-Memory persistence is used.
With CMCC 13 the default will be changed to sql.
Until then, you can use the Spring profile sql
to switch to SQL persistence for all features relevant for the respective application.
The profiles will set the following properties:
-
Studio Server:
workflow.server.archive.persistence=sql caplist.persistence=sql notification.persistence=sql project.persistence=sql
-
User Changes:
caplist.persistence=sql notification.persistence=sql
-
Workflow Server:
workflow.server.archive.persistence=sql caplist.persistence=sql
