CoreMedia's collaborative components store their data in separate schemas in an SQL database. The database itself can be the same that is used for the Content Servers, but it does not have to be.

Note

Previous versions used a MongoDB database for the collaborative components. This is no longer supported except for data migration to the new SQL persistence layer.

The database properties are configurable per feature using these prefixes:

For each of these features you can configure the persistence which now defaults to sql. In previous versions it was set to elastic-core. While you can still enable elastic-core persistence, it is no longer supported and will be removed in future versions. But, you can still use it to prepare or check your data for migration 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

To enable elastic-core persistence, you can use the Spring profile elastic, or set the following properties:

For detailed description of configuration properties, please see: