Operations Basics / Version 2512.0
Table Of Contents
Deprecation Notice
The MongoDB persistence for Editorial Services is deprecated and will be removed in a future release. It is recommended to use the SQL persistence. This section is only kept for migration purposes as reference for your existing in-memory configuration.
| Property | Example | Description |
|---|---|---|
mongodb.client-uri
|
mongodb://<Username>:<Password>@<Host>:<Port>/
|
The URL of the MongoDB to connect to. Replace <Username>,
<Password>, <Host> and
<Port> with the appropriate values of the MongoDB installation. Add
this property to the WEB-INF/application.properties file of
Studio, User Changes Application and
Workflow Server,
and let it point to your MongoDB.
|
mongodb.prefix
|
<prefix>
|
When the collaborative components persist collaboration data to a
MongoDB database, the default name of its database is
prefixed by blueprint. To configure a different database name prefix, add
this property to WEB-INF/application.properties files of
Studio, User Changes Application and
Workflow Server>.
|
Table 4.10. Properties for persistence of collaboration data to MongoDB
MongoDB Authentication
MongoDB authentication is enabled on deployment level, and the user coremedia/coremedia is created by default.
Authentication is performed against the admin database. Example:
use admin
db.auth('coremedia','coremedia')The default mongodb.client-uri is configured with credentials, for example
mongodb.client-uri=mongodb://coremedia:coremedia@${installation.host}:27017For development with a MongoDB without authentication, either remove the credentials prefix from the
mongodb.client-uri property or create a user with:
use admin
db.createUser({user: 'coremedia', pwd: 'coremedia', roles: ['userAdminAnyDatabase', 'dbAdminAnyDatabase', 'readWriteAnyDatabase']});