Deployment Manual / Version 2107
Table Of ContentsThe following table lists the configuration properties for the CoreMedia Editorial Comments feature, which establishes a connection to the relational database.
The most important property is editorial.comments.datasource.url which sets the URL to connect to.
In case another schema/username/password
has to be configured use the properties editorial.comments.db.schema/editorial.comments.db.username/editorial.comments.db.password.
editorial.comments.datasource.driver-class-name
| |
| Type | java.lang.String |
| Default | |
| Description | Required to be set according to your database. See official spring documentation 'spring.datasource.driver-class-name' for detailed information |
editorial.comments.datasource.hikari.connection-timeout
| |
| Type | java.lang.Integer |
| Default | 20000ms |
| Description | Value must not be greater then the studio request timeout. See official spring documentation 'spring.datasource.hikari.connection-timeout' for more information |
editorial.comments.datasource.password
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official spring documentation 'spring.datasource.password' for more information |
editorial.comments.datasource.url
| |
| Type | java.lang.String |
| Default | |
| Description | Required to be set according to your database. See official spring documentation 'spring.datasource.url' for detailed information |
editorial.comments.datasource.username
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official spring documentation 'spring.datasource.username' for more information |
editorial.comments.db.password
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | Use to set the password for hibernate and liquibase. |
editorial.comments.db.schema
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | Use to set the schema for hibernate and liquibase. |
editorial.comments.db.username
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | Use to set the username for hibernate and liquibase. |
editorial.comments.jpa.database-platform
| |
| Type | java.lang.String |
| Default | |
| Description | See official spring documentation 'spring.jpa.properties.hibernate.database-platform' for detailed information |
editorial.comments.jpa.properties.hibernate.default_schema
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official spring documentation 'spring.jpa.properties.hibernate.default_schema' for more information |
editorial.comments.liquibase.change-log
| |
| Type | java.lang.String |
| Default | classpath:db/changelog/db.changelog-editorial-comments.xml |
| Description | See official liquibase documentation 'liquibase.change-log' for more information |
editorial.comments.liquibase.default-schema
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official liquibase documentation 'liquibase.default-schema' for more information |
editorial.comments.liquibase.enabled
| |
| Type | java.lang.Boolean |
| Default | true |
| Description | Use this property to disable liquibase, however this means that you need to apply the changesets to the database manually. You can either do that by activating liquibase for at least one startup of a Studio-Server, or run liquibase manually (https://docs.liquibase.com/tools-integrations/cli/home.html) after an upgrade. |
editorial.comments.liquibase.password
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official liquibase documentation 'liquibase.password' for more information |
editorial.comments.liquibase.user
| |
| Type | java.lang.String |
| Default | cm_editorial_comments |
| Description | See official liquibase documentation 'liquibase.user' for more information |
editorial.comments.notification-strategies.created-comment-on-content
| |
| Type | java.lang.Boolean |
| Default | true |
| Description | This property enables the CreatedCommentOnContentCollectUsersToNotifyStrategy which collects all users who wrote a comment at this content in the last 30 days. True if the strategy is enabled, false if the strategy is disabled. |
editorial.comments.notification-strategies.edited-content-in-last-thirty-days
| |
| Type | java.lang.Boolean |
| Default | true |
| Description | This property enables the EditedContentInLastThirtyDaysCollectUsersToNotifyStrategy which collects all users who edited the given content in last 30 days. True if the strategy is enabled, false if the strategy is disabled. |
editorial.comments.notification-strategies.my-edited-contents
| |
| Type | java.lang.Boolean |
| Default | true |
| Description | This property enables the MyEditedContentsCollectUsersToNotifyStrategy, which notifies every user that has the Content where an EditorialComment was created for in his "myEditedContent" List. true if the strategy is enabled, false if the strategy is disabled. |
Table 4.31. Editorial Comments Properties
Note
If the startup of a Studio-Server instance has been interrupted, it is possible that a lock is left by Liquibase on the database schema cm_editorial_comments.
In this case it is necessary to remove the lock manually, as described at https://docs.liquibase.com/concepts/basic/databasechangeloglock-table.html.
It is also possible to disable Liquibase with the configuration editorial.comments.liquibase.enabled
(for further details, refer to Section 3.5, “Editorial Comments Database Configuration” in Studio Developer Manual).
